Dear Experts ..

   This following statement is from Help.sap  "In SAP Accounting powered by SAP HANA only new Asset Accounting is available with new General Ledger Accounting. For you to be able to use new Asset Accounting, you need to have activated and set up the General Ledger Accounting (FI-GL) (New) application component"

Assuming that my system is on ECC 6.0 (EHP 7.X) on HANA DB. using classic GL and classic asset accounting I am planning to move to SFIN with New AA.. so first should I move on to new AA and then migrate to SFIN.? but its confusing whether its a parallel (AA & GL) move or which one should be first done old AA to NEW AA or classic GL to  SFIN?

According to AC110/100 books for SFIN I have read that New AA is only option in SFIN and old AA is not supported and you need to be on NEW GL in order to use New AA. and further its mentioed that you can migrate to NEW GL inside SFIN..

Can someone please clarify this part whether first moving to new AA  and then migrating from classic gl on ecc 6.0 (ehp 7.x with HANA DB) to SFIN will directly land us techincally to new gl in SFIN ? and so that we can directly use new AA without any futher steps

or migration inside SFIN  GL to new GL is required [after adding simple finance add] for using Asset accounting.?

Dear Friends/experts,

   Please clarify my doubts regarding the following (urgent help is required)

1.   We have a ECC 6.0  on EHP 7.4 on top of SAP HANA DB system running on Classic GL and Classic AA (DEV system), We have started      copying Prod data into dev as beggining of the project
2.   In Dev we will activate (EA-FIN) component and then install Simple finance add on
3.   Run pre migration checks and migrate to General ledger on SFIN customizing settings ( no need of any new gl funcionality) DO post migration ativity in DEV and Migrate transaction data
4. Activate New AA, Run pre migration activity for NEW AA (period close activities ) and Migrate Chart of Dep during 1st of new period, Migrate Transaction Data
5. Migration of Bank accounts
6. Check for custom objects and apply if any fixes required

Now the major question is after DEV is complete.. how do I move forward with Acceptance ? (i.e) Transport all customising activities including SFIN/NewAA/Custom objects to Acceptance box Copy latest prod data and run migration program only for transaction data ? or

Rebuild the Acceptance as DEV? I am totally confused at this stage and could not proceed please throw some light into the landscape movement also for production scenario

As per my understanding after activating (EA-FIN) and then installing SFIN in Dev we will do the baseline configurations required (pre migration activities) as part of SFIN migration in DEV for GL & AA and then run the migration program that will migrate customizing data and transaction data in DEV client and will that not generate any transports (I specifically mean migration programs regarding customizing data that needs to be moved to Acceptance )

So for UAT in acceptance we will move the customizing transports generated (baseline config as above along with clients custom objects) to Acceptance box and do I need to again install (SFIN) hope this wll come from DEV itself  and have a latest production copy in A box and again run the migration programs again to verify if everything is working fine to get business sign off?

This part is not clear in AC 100 itself .. because i am unsure about what I will test in UAT is it only the fresh transaction data from logistics & Finance modules? how will the migration activities handled in Acceptance and Prod.. Please give your inputs .

Hi HANA Gurus,

We are planning to migrate from Non-SAP system into S4 HANA. I have couple of doubts I need your inputs.

1. If we use SLT, I understand it will replicate table into HANA Database. But How to get that data on HANA Application? For example: I get MARA table replicated into HANA DB and I can see contents using HANA Studio but does it mean I will see same content if I use SE16 on S4 HANA Application?

Is there any step I need to do 'after' Replication is done??

2. Other doubt I have is, considering I have few transformation requirements. Will SLT be right tool? or shall I go with BODS? or SDI? Our leadership is very inclined towards using SLT. Just wondering if that would be right tool (considering SLT now supports Non-SAP system plus some transformations too now I suppose)

Kindly suggest please

Greetings

We are implementing S4HANA, and we are customizing revenue accounting 1.1; We have already done Revenue contracts and POBs, but all of them have had "transaction price" in Zero; the condition type that we are using is “PR00” (Customizing “Define Condition Types for Standalone Selling Price and …”) and in the transaction VK11 we have created stand-alone prices for this, but I still having the issue.

We have created the 3 application that the help configuration says in BRF+, also we have filled the decision table "DT_PROCESS_POB" and the POB Type, with the field "Excl. from Alloc." with value "X" because we need that the invoice price and the contract price will be the same. There is not much information about how create rules in BRF+, but at this time, only at the price determination we have had problems; We need resolve this issue for follow with the account determination and review the posting.

Your help for know what we are missing for get the price of the invoice in the contract price or transaction Price.

Hi everybody

I am in a project where we need to implement Deferred revenue when the invoice (in SD) is created and with another event ( performance obligation: boarding boat) recognice the revenue.

I am FI consultant and with another SD consultant we read about "ERP SD Revenue Recognition", but in the s4hana on premise 1511 that we're going to implement says that we have to use "SAP Revenue Accounting and Reporting".

There is not much information about this, i have done the configuration but i can´t pass of this error:

Reserved condition types are not configured in Customizing

Message no. FARR_CONTRACT_DB033

Required field 'Fulfillment Type' of performance obligation $000000000000001 is empty

Message no. FARR_CONTRACT_MAIN000

Required field 'Event Type' of performance obligation $000000000000001 is empty

Message no. FARR_CONTRACT_MAIN000

I appreciate your support for these error; I have filled some desicion tables but i the error continues...

Thanks!

Hi Team

Iam  getting below error message at various places (particularly when i tried to change rules for take over)  and pls find the details below for your valuable suggestion to resolve the issue. Not able to change from 01 to 00 for dep area 30

Hi everyone!

Recently, we updated Simple Finance, On-Premise Edition SPS02 to SPS04

Now, we are trying to execute FF7AN & FF7AB Reports (included in SPS04 -> 2255996 - SFIN Support for Cash Position and Liquidity Forecast Reports in New Cash Management), but this dump is triggerred;

Category                      ABAP Programming Error

Runtime Errors             AMDP_EXECUTION_FAILED

Except.                        CX_AMDP_EXECUTION_FAILED

ABAP Program             CL_FFHN_FLOW_CONVERSION=======CP

Application Component  FIN-FSCM-CLM-CM-CM

Date and Time              23.05.2016 17:16:07

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

Short Text                                                                                  

    Error while executing a database procedure                               

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

What happened?                                                                                   

    During execution of database procedure                                                     

    CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR                                                   

    an error occurred.                                                                           

    SQL code of the database: 7                                                                  

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

Error analysis                                                                                    

     An exception has occurred which is explained in more detail below. The                        

     exception is assigned to class 'CX_AMDP_EXECUTION_FAILED' and was not caught                  

      in procedure                                                                                 

     "CONVERT_FLOW_CURR" "(METHOD)", nor was it propagated by a RAISING clause.                    

     Since the caller of the procedure could not have anticipated this                             

     exception, the current program was terminated.                                                

     The reason for the exception is:                                                              

     When calling database procedure                                                               

     CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR                                                    

     an error occurred. The error message begins with (full message under                          

     "Information about database procedures (AMDP)":                                               

     "feature not supported:  [7]                                                                  

      "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR#stb2#20160516233826":                 

      line 10 col 3 (at pos 289): [7] (range 3): feature not supported:  [7]                       

      "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR": line 15 col 5 (at                   

      pos "                                                                                        

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

How to correct the error                                                                          

     The exception must either be prevented, caught in procedure                                   

      "CONVERT_FLOW_CURR" "(METHOD)", or                                                           

     the possibility of it occurring must be declared in the RAISING clause                        

     in the procedure.                                                                             

     To prevent the exception, note the following:                                                 

     You can find the full text of the error message under "Information                            

     about database procedures (AMDP)". Correct any programming errors you                         

     encounter in                                                                                  

     "CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR".                                                 

     Maybe                                                                                         

     CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR                                                    

     was called by another database procedure. The method called from ABAP                         

     is                                                                                            

     "CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR".                                                 

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

Information on where terminated                                                                   

     The termination occurred in ABAP program "CL_FFHN_FLOW_CONVERSION=======CP",                  

      in "CONVERT_FLOW_CURR". The main program                                                     

     was "RFTS7000".                                                                               

     In the source code, the termination point is in line 13 of (Include)                          

     program "CL_FFHN_FLOW_CONVERSION=======CM002".                                                

     The termination is due to exception "CX_AMDP_EXECUTION_FAILED" occurring in                   

      procedure "CONVERT_FLOW_CURR" "(METHOD)".                                                    

     This exception was not handled locally or declared in the RAISING                             

     clause in the procedure's signature however.                                                  

     The procedure is in program "CL_FFHN_FQM_INTRG=============CP        ". The                   

      source code begins in line 1 of                                                              

     (include) program "CL_FFHN_FQM_INTRG=============CM00H     ".                                 

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

Database Procedure (AMDP) Information                                                             

     Full Error Message from the Database:                                                         

     feature not supported:  [7]                                                                   

     "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR#stb2#20160516233826": line 10 col 3    

     (at pos 289): [7] (range 3): feature not supported:  [7]                                      

     "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR": line 15 col 5 (at pos 470): [7]      

     (range 3): feature not supported: Converter creation is disabled. Please enable conversion    

     and try again!Please check lines: 49,39,36,19,15,                                             

     Active Calls in the Database:                                                                 

     CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR: line 15 col 5                                     

     CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR#stb2#20160516233826: line 10 col 3                 

     Datatbase Connection Used:                                                                    

     <default>                                                                                     

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

Here in bolded some interesting points;

• SQL code of the database: 7     

• "feature not supported:  [7]                                                                  

      "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR#stb2#20160516233826":                 

      line 10 col 3 (at pos 289): [7] (range 3): feature not supported:  [7]                       

      "SAPABAP1"."CL_FFHN_FLOW_CONVERSION=>CONVERT_FLOW_CURR": line 15 col 5 (at                   

      pos "

*feature not supported ?

• feature not supported: Converter creation is disabled. Please enable conversion and try again!Please check lines: 49,39,36,19,15,

*Converter creation is disabled? Where sounds that i could enable this feature? In HDB, in Customizing? some business function?

*HDB Release: 1.00.097.00.1434028111

Any suggestion for this issue?

Regards...!

Hi everyone,

Does anybody know availabilty date for S/4HANA Finance 1605, according to road map it should be released in May, but cannot find information when exactly?

Best regards,

Tomislav

Using ME21N to create PO, and clicked on "Varient option". It threw an error and "Variant SAP&MEBANF of program AQZZ/SAPQUERY/MEMEBANF============ is not the current version".

Screen frozen, and I have to come log off everytime. How can I make sure, that I create a Purchase Order using Purchase Requisition Variant.

Thanks.

Dear Friends,

    Please calrify the following "To use this solution New AA, prerequisite is the use New GL Accounting with Ledger Approach. Prior

to New Asset Accounting",

  I am on Classic GL with Accounts approach and planning to migrate to Simple finance which will land me in tecnical new gl after completing all prerequsites/ migration/post migration activities along with migration of classic AA.....Is it enough for me to use New AA ? or prior to that I need to first migrate to New gl in Ecc 6.0?

Please clarify this part of using new AA while migrating from classic GL to S4 GL (I dont need any functionalities of new gl presently)

Hello Everyone,

I have a question please , now im working on SAP S Fin 1511 edition , is there any tool to use the classic transaction codes on ERP such as FD01,FK01??? waiting for your reply

In the latest version of S/4 HANA 1511, most processes was relocated into the Universal Journal table "ACDOCA ", not the table "BSEG" anymore. During the work based on S/4 these days, this change may have cause the following problem:

For some official ALV report programs, like "FBL3N" and "IDCNCASH", this change may cause the data is not correct. Like foreign currency valuation, relevant processes is not in the old table "BSEG", but in the new table "ACDOCA". However "ACDOCA" is lack of the useful column: Reason Code RSTGR. Is there any other column which I can figure out the reason code?

Looking forward for your reply.

Hello everybody! I need some help over here!

I wanted to ask you guys:

will like to ask you a question concerning tax returns for corporations in the USA.

The S/4 HANA 1511 and previous versions can send tax returns(form 1120, for example)

to the Internal Revenue Service (IRS) via e - file (or by others means)?

Or if you know where I can look for this information.

Thank you guys!!

Sincerely,

Alejandro

Dear All,

I am trying to execute query

/ERP/SFIN_V01_Q2701

I am getting this error

Could not determine value of variable 0P_FVAEX or (0P_CTPCA)

Any help would be appreciated.

Thank you,

Sunil

Hello,

I will like to ask you a question concerning tax returns in the USA.

The S/4 HANA 1511 (and previous versions) can send corporations tax returns

(form 1120, for example) to the Internal Revenue Service (IRS) via e - file (or by

others means)? or if I have to use a third party software?

Thank for your help.

Sincerely,

Alejandro

Hello,

I was curious to know if we have information regarding the upcoming release for S/4HANA Finance on premise edition will be? Will it be 1605 or 1608. We are considering to do a proof of concept and would like to do that on the latest version of it even if it means waiting for a few months.

Cheers!

Dan

Hello everyone!

After activate the business function FIN_FSCM_CLM, the customizing IMG for Cash Management powered by S4HANA shows. I have already done the configuration of the Planning Levels ans Planning Groups, but when I create a FB70 the field "Planned Level" and the "Planned Date" do not appears.

Of course, the master record of the customer has assigned a "Planned group".

What i am missing?

thanks!

Hi Folks,

Already company using version ECC6.0 but now company want to implement sap hana on premises. What are the steps need to be take care of in simple finance. If we want to implement any road line map for the same in finance side as like as asap methodology. If yes, Please share the road map for simple finance.

If we implemented sap hana simple finance, what are the areas impacting like GL, Asset, AR, AP etc.....

if any additional information is require, Please suggest.

Regards,

Venkat

Hi everybody

I am in a project where we need to implement Deferred revenue when the invoice (in SD) is created and with another event ( performance obligation: boarding boat) recognice the revenue.

I am FI consultant and with another SD consultant we read about "ERP SD Revenue Recognition", but in the s4hana on premise 1511 that we're going to implement says that we have to use "SAP Revenue Accounting and Reporting".

There is not much information about this, i have done the configuration but i can´t pass of this error:

Reserved condition types are not configured in Customizing

Message no. FARR_CONTRACT_DB033

Required field 'Fulfillment Type' of performance obligation $000000000000001 is empty

Message no. FARR_CONTRACT_MAIN000

Required field 'Event Type' of performance obligation $000000000000001 is empty

Message no. FARR_CONTRACT_MAIN000

I appreciate your support for these error; I have filled some desicion tables but i the error continues...

Thanks!