SAP Support for Classic G/L in ECC 6.0 and above

Hello,
Running an SAP upgrade project from 4.6C to ECC 6.0 (EHP6). The customer is running the existing release since the past 8 years with FI/CO, MM,SD,PM and HCM modules.
We are exploring the possibilities and repercussions of moving on to new G/L from the legacy classic G/L. Please have a look at the mentioned points for replies accordingly.
1. As far as I understand, if need to seamlessly transit in the ECC 6.0 with New G/L in a way that the old transactional data, and all balances are retained with historical records, then we need to purchase the SAP New G/L Migration Services, and this would be lead and done by SAP. There is no alternate way of doing it solely by our ownself, Is this correct ?. If we engage SAP for this migration exercise and consulting then does it ensure that all historical data and balances are moved intact in the new G/L environment and from an end user perspective all transactional done to date before moving in ECC 6.0 are retained.
2. I guess we still need to review the integration impact of the new G/L for all other modules, is there a substantial rework to be done or with minimal effort, new account assignments and related configuration can be altered .
3. If we don't opt for SAP G/L Migration service but still want to activate and use the new G/L and profit center accounting, then as far as myself and my team assess, we need to decide a cutover date and gather the balances/open items from the legacy G/L and upload them to the new G/L in ECC 6.0, just as it would be the case for a fresh new implementation for a customer coming from non-SAP environment. If this is correct then :
The customer will lose all historical, detailed transactional data with respect to the legacy G/L and relevant originating entries. In such case for any business reporting requirement, the customer has to keep a separate PRD server alive in a dormant state for fetching the data before the transition in ECC 6.0 environment. Is this the correct understanding and the only possible approach, can there be a better way of ensuring the availability of historical data.
In such a case of doing a cutover data migration from old G/L to new G/L, do we have to upload the rest of the master/transactional data for all other modules as well, enacting a situation that all of them started as fresh new modules in ECC.6.0, or the legacy master / transactional data for all other modules can be kept intact for historical purposes. (examples, all vendors and PO / sales order and customer master / employee master and all payroll historical records for past 8 years).
4. Any indication or official SAP note, that for how long SAP intends to support the legacy G/L in the upcoming ECC versions. It is necessary to know in case the customer currently opts for still continuing with the classic G/L in ECC 6.0 , but we have a lurking danger that SAP would stop the support and availability of legacy classic G/L in the near future. So to a have a long term sustainable benefit, we might deliberate with the customer to take a bitter sip now , and move on to the new G/L with all its bells/whistles and the nuisances it might bring in terms of historical transaction data unavailability.
I hope i was able to make my scenario clearly understandable for having some valuable input from the forum members.
Thanks a lot for reading and replying.

Hi Syed,
From Technical basis perspective there is not much work in newGL migration apart from application and database tuning.
Time taken for migrating to newGL will depend upon number of open items available in the system at the time of migration.
Most of your queries are functional and suggestion would be to move this thread to ERP Financials.
For your information you may go through below links
http://help.sap.com/saphelp_erp60_sp/helpdata/en/ae/b3569044974c6985c4e711e20435d6/content.htm
http://wiki.scn.sap.com/wiki/display/ERPFI/NewGL+Migration+Scenarios
Hope this helps.
Regards,
Deepak Kori

Similar Messages

Support for Classic planning applications

Hi,
We have developed planning applicaiton using classic. Our client says that the support for classic planning applications will be withheld by oracle and so they want us to convert the classic to EPMA. Is it true that the support will be withheld?
Also it is not possible to load metadata to EPMA applications using Outlineload utility. Am i right?
Regards,
Ragav.

ragavhere wrote:
Hi,
We have developed planning applicaiton using classic. Our client says that the support for classic planning applications will be withheld by oracle and so they want us to convert the classic to EPMA. Is it true that the support will be withheld?
Also it is not possible to load metadata to EPMA applications using Outlineload utility. Am i right?
Regards,
Ragav.I have never heard that mentioned by anybody, there are many classic applications out there that use outline loader, ODI, DIM to manage the planning applications metadata.
No you can't use the outline loader for EPMA, but there is a command line utility :- http://download.oracle.com/docs/cd/E17236_01/epm.1112/epma_batch_user/launch.html
Cheers
John
http://john-goodwin.blogspot.com/

Until when give SAP support for version 7.30?

Hello,
Until when give SAP support for version 7.30?
How is the update from SAP GUI 7.30 to 7.40 handle?

Hello Herr Jürs,
As per the attached note http://service.sap.com/sap/support/notes/147519
support ends in July
SAP GUI for Windows Support Deadlines
7.30: Full support up to July 15th, 2015. On July 15th, 2015 the used development environment Microsoft Visual Studio 2010 will transit to Microsoft's "Extended Maintenance" mode. This means that Microsoft will not create any corrections for components which belong to this development environment anymore (unless the issue is security relevant). Therefore no extension of full support for SAP GUI for Windows 7.30 beyond this date is possible.
Regards,
Jude

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (.m4v). I have not touched the file in any way (no trimming, clipping or other editing)

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (e.g. .m4v). I have not touched the file in any way (no trimming, clipping or other editing), all I want QuickTime to do is export the file in a compressed format. Bizzarely, if I shutdown and open QuickTime many times I can occasionally export a clip as another format (maybe one in 10 times). I have seen that other users have had a similar problem after clipping files in QuickTime but this seems to be a slightly different bug in that all I do is open the file and then try and export the file as is - either way, this is a very annoying bug

@Z_B-B, thank you for taking the time to respond to my cry for help. However, the link you supplied does not address the problem: I am not trying to export from Final Cut Pro to QuickTime, I am trying to export from QuickTime to the rest of the world (like people's iPhones and Ipads) in .m4v format (so I am not emailing my freinds such huge files).
If I were to spend hundreds of Dollars on a copy of Final Pro I could export directly from there and not have to bother with QuickTime, but I do not take enough video clips to justify the cost. I must say that I never had any of these problems before I decided to switch from Snow Leopard to Mountai Lion.

HT5815 im searching a for a update there makes it possible for mac computer with OS X To play games there aren't Supported for power pc, Like Warcraft 3, Diablo 2 and those kind of old games there worked on the previous versions of the OS

im searching a for a update there makes it possible for mac computer with OS X To play games there aren't Supported for power pc, Like Warcraft 3, Diablo 2 and those kind of old games there worked on the previous versions of the OS

Here is a thread for you: Is there any possible way to run PPC...: Apple Support Communities

Users working in version ECC 6.0 and above

hi
I need some help, I am trying to run this code on my system but not able to get the desired result,
i just want to test whether other users working on ECC 6.0 and above can run this code from their system.
Just copy, paste and run this code... I will get an e-mail automatically, I shall reward points in return, please help me with this...
REPORT bcs_example_5.
* This example shows how to send
*   - a simple text provided in an internal table of text lines
*   - and an attached MS word document provided in internal table
*   - to some internet email address.
* All activities done via facade CL_BCS!
DATA: send_request       TYPE REF TO cl_bcs.
DATA: text               TYPE bcsy_text.
data: binary_content     type solix_tab.
DATA: document           TYPE REF TO cl_document_bcs.
DATA: sender             TYPE REF TO cl_sapuser_bcs.
DATA: recipient          TYPE REF TO if_recipient_bcs.
DATA: bcs_exception      type ref to cx_bcs.
data: sent_to_all        type os_boolean.
START-OF-SELECTION.
    PERFORM main.
*       FORM main                                                     *
FORM main.
try.
*     -------- create persistent send request ------------------------
      send_request = cl_bcs=>create_persistent( ).
*     -------- create and set document with attachment ---------------
*     create document from internal table with text
      APPEND 'Hello world!' TO text.
      document = cl_document_bcs=>create_document(
                      i_type    = 'RAW'
                      i_text    = text
                      i_length = '12'
                      i_subject = '' ).
*     add attachment to document
*     BCS expects document content here e.g. from document upload
*     binary_content = ...
      CALL METHOD document->add_attachment
        EXPORTING i_attachment_type = 'DOC'
                   i_attachment_subject = 'My attachment'
                   i_att_content_hex    = binary_content.
*subject line more than 50 chars
      DATA: T_SUB TYPE STRING.
      t_sub = '[ D01 TEST] CCS0000096 NJ 8A7192 21 CONSTITUTION AVE'.
      call method send_request->set_message_subject( t_sub ).
*     add document to send request
      CALL METHOD send_request->set_document( document ).
*     --------- set sender -------------------------------------------
*     note: this is necessary only if you want to set the sender
*           different from actual user (SY-UNAME). Otherwise sender is
*           set automatically with actual user.
      sender = cl_sapuser_bcs=>create( sy-uname ).
      CALL METHOD send_request->set_sender
        EXPORTING i_sender = sender.
*     --------- add recipient (e-mail address) -----------------------
*     create recipient - please replace e-mail address !!!
      recipient = cl_cam_address_bcs=>create_internet_address(
                                        '[email protected]' ).
* To send the mail immediately
      call method send_request->set_send_immediately( 'X' ).
*     add recipient with its respective attributes to send request
      CALL METHOD send_request->add_recipient
        EXPORTING
          i_recipient = recipient
          i_express    = 'X'.
*     ---------- send document ---------------------------------------
      CALL METHOD send_request->send(
        exporting
          i_with_error_screen = 'X'
        receiving
          result              = sent_to_all ).
      if sent_to_all = 'X'.
        write text-003.
      endif.
      COMMIT WORK.
* *                     exception handling
* * replace this very rudimentary exception handling
* * with your own one !!!
catch cx_bcs into bcs_exception.
    write: 'Fehler aufgetreten.'(001).
    write: 'Fehlertyp:'(002), bcs_exception->error_type.
    exit.
endtry.
ENDFORM.

Hi,
The following code is i have done in ECC 6.0 working fine for me. May this one help you in anyway.
data: send_request       type ref to cl_bcs.
data: document           type ref to cl_document_bcs.
data: sender             type ref to cl_sapuser_bcs.
data: recipient          type ref to if_recipient_bcs.
data: exception_info     type ref to if_os_exception_info,
bcs_exception            type ref to cx_document_bcs.
data i_attachment_size type sood-objlen.
data v_status          type bcs_stml.
data v_request_status type bcs_rqst.
send_request = cl_bcs=>create_persistent( ).
try.
      document = cl_document_bcs=>create_document(
                                    i_type    = 'RAW'
                                    i_text = it_content[]
                                    i_subject = subject ).
      if not attach_name1 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext1
            i_attachment_subject = attach_name1
            i_att_content_text   = it_attach1[].
      endif.
      if not attach_name2 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext2
            i_attachment_subject = attach_name2
            i_att_content_text   = it_attach2[].
      endif.
      if not attach_name3 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext3
            i_attachment_subject = attach_name3
            i_att_content_text   = it_attach3[].
      endif.
      if not attach_name4 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext4
            i_attachment_subject = attach_name4
            i_att_content_text   = it_attach4[].
      endif.
      if not attach_name5 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext5
            i_attachment_subject = attach_name5
            i_att_content_text   = it_attach5[].
      endif.
      call method send_request->set_document( document ).
      sender = cl_sapuser_bcs=>create( sy-uname ).
      call method send_request->set_sender
        exporting
          i_sender = sender.
      loop at it_recipient.
        translate it_recipient-smtp_addr to lower case.
        recipient = cl_cam_address_bcs=>create_internet_address( it_recipient-smtp_addr ).
        call method send_request->add_recipient
          exporting
            i_recipient = recipient
            i_express    = ' '
            i_copy       = ' '
            i_blind_copy = ' '
            i_no_forward = ' '.
      endloop.
      move : 'E' to v_request_status.
      v_status = v_request_status.
      call method send_request->set_status_attributes
        exporting
          i_requested_status = v_request_status
          i_status_mail      = v_status.
      call method send_request->send( ).
      commit work.
    catch cx_document_bcs into bcs_exception.
endtry.
I could not able to check your code in development boxes of mine . sorry.
aRs

Sap support for standard prog. w/ custom implem of implicit enhanc.points

Hello,
since 1 year I've been confronted to SAP customers which WIDELY implement Implicit Enhancement Points (IEP).
I have been really surprised that my customers undoubtly think, if a problem occurs in a standard program where there are lots of IEP custom implementations, and if my customers estimate after investigation the problem comes from the standard part and not from the IEPs, they think that SAP support would help them to solve the issue.
Note: as a consequence, they created much more IEP in ECC 6 than they did in the past with R/3 old releases (via changes of the standard, aka repairs)!
What I think, is that SAP SUPPORT WOULDN'T HELP them as long as there is custom code (even within IEPs) in the standard program, even if there is only one IEP with one line (because it could change completely the standard algorithm, for example by emptying a global internal table)
So, I think the only way to get help from SAP is to deactivate these IEP implementations before requesting support. And so, the only solution to deactivate them, customers MUST assign IEP implementations to a package and then to a switch and then to a business function, so that they can deactivate it via switch framework.
The main concern is that my customers didn't create switch/business function, so they cannot react quickly if a problem happens in production : reproduce in test system, deactivate custom IEPs by switching off business function (it's what they didn't do), reproduce with full standard to determine problem comes from standard, request help from sap).
Could you share with me what is your approach about implementing IEPs, and maybe, is there somewhere a SAP documentation which explains that officially?
I hope I was clear.
Thank you very much for your kind help.
Best regards,
sandra rossi

I played around a bit with this (as I had never done it before) and also from what I have read, the intended option is the switch framework.
I guess as plan B you could have a virtual system or reliable test environment in which you can disable the enhancement and bring it back again via version management - but from what you have described (IEP deleting gobal variables, etc) this would also remove the "bug" and make the problem difficult to reproduce.
Perhaps the next best thing (unless someone has a better idea) is to inform your customers about neatly organizing their software developments using packages and switches.
To my knowledge, the syntax checks are also getting stricter in this area (as you may have noticed) and I hope that (for some of them) will throw errors one day during the development stage already.
Sorry, that does not help you much (but at least you read "the rules"
Cheers,
Julius
ps: A dirty way of doing it would be to run the program in the new debugger, and skip over the enhancement using the Go-To function. Unlike the classic debugger, the code inbetween does not need to be debugged. Ugly, but effective...
Edited by: Julius Bussche on Nov 10, 2008 9:13 PM

Migration and SAP Support for BW 3.1

Hi,
I have couple of queries regarding Migration and SAP Support.
What is the required patch level that need to be mantained in BW 3.1 for a direct upgrade to BI 7.
I would like to know whether SAP still supports BW 3.1. I searched in SAP Service marketplace, but didn't get much information regarding this.
Your inputs are highly appreciated.
Regards,
Hari

Hello,
BW Upgrade from 3.x to 7.0
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e62b9990-0201-0010-42a7-ddcf5c93cafd
Hope it will help you.
Regards,

SAP Support for Windows 2008 R2 SP1

How can I find out if SAP supports Windows 2008 R2 SP1?
We have ECC6 enh4 running on Win2008R2 servers, our admin would like to apply SP1 to these. I'm trying to find documentation to verify SAP Supports SP1. So far I've come up empty.
Thanks

Hello Laurie,
The up to date kernels support Windows 2008R2
SAP supports the following 64-bit (x64, IA64) Windows Server 2008 R2 editions:
Standard edition, Enterprise edition, Datacenter edition, and for Itanium-Based Systems edition
Windows Server 2008 R2 Server Core is not supported by SAP.
See url
SAP on Microsoft Windows
Hope it's work for you,
Ignacio.

SAP support for country-specific legal requirements

Just wondering if anyone could clarify how does SAP support work for the country-specific legal requirements. I'm sure in every country some new laws come to life regularly that affect the SAP customers and their ERP systems.
Case in point - on July 1st Mexican authority SAT decided to ask businesses to send them some XML files with some GL account information ('Anexo 24' - see the announcement in Spanish here). The deadline for the first file submission is October 2014.
This clearly affects every single SAP customer in the whole Mexico, as well as potentially many North America customers who have manufacturing facilities there. So would it be reasonable to expect SAP to come up with some standard solution? XML file extraction doesn't seem to be incredibly complex to me (although I might be off).
Another question - how would the customers know that SAP is aware of new laws and is taking some action? Could there be an announcement posted somewhere? There is a website for SAP Latin Americabut the latest announcement there is from June and nothing else is on the home page except for the HANA ads. (My Spanish is limited to "dos cervezas por favor", sorry if I missed something.)
In absence of such communication, naturally, the only option the individual customers have is to send a message to SAP. And that's where SAP replies with a copy/paste text (we got the same exact response as another SCN member here):
Feel free to maintain this incident opened, but contact us in the next three weeks, then we will be able to confirm if this legal requirement will be supported by SAP.
I'm confused - "IF"?! This is a legal requirement, there is no "if" for the business. Let's see if I got it right - we wait for 3 weeks, then SAP decides "nah, not gonna support that" (by the way, why is it on the customers to contact support again?) and every SAP customer in the whole country will have to scramble their own resources or pay for consulting (on top of SAP maintenance fees) to deliver the same exact set of programs on their own in under 2 months?
It could've been just an unfortunate choice of verbiage by Global Support, but I'm curious - is this really how the support for legal requirements supposed to work?
Thank you.

Hi Jelena,
Having been part of the SAP Globalization Services in Brazil, I understand a little bit of that process.
A few comments:
1) Localization of SAP solutions to country-specific regulation is under the responsibility of an area called Globalization Services. You can find more info about what they do here:
http://service.sap.com/globalization
2) Typically, those country-specific requirements are discussed in much details on the local ASUG chapters (at least that's how we did it in Brazil). That's why it's usually hard to find material in English, but I'd say that your local IT/Biz people in Mexico should be regulars in their local ASUG meetings, specially if they have a specific chapter to discuss Localization matters.
3) I found out this note with more specifics about "SAT Anexo 24".
http://service.sap.com/sap/support/notes/2041490
Apparently SAP is still analyzing it.
Suggestion if you want to speed the analysis up: reach out to your commercial contact in SAP.
4) Regarding your statement about the time it takes for the analysis & delivery to take place.
As an SAP customer, you have all the right to complain about the service level you're getting, it's just that, having been on the other side of the table, I know some facts that sometimes may be taken for granted. For example, SAP do not have infinite maintenance resources. I do understand that all customers pay maintenance and need to have their demands addressed, but SAP does not have a bench of developers available for whenever a new demand appears. If there is a new demand, they need to estimate the efforts and accommodate it into the development resource planning.
5) From a legal perspective, there is a difference between Legal Change and New Legal Requirement. The latter, if differing too much from the initial purpose of the acquired software, might not necessarily be required by the Software provider to be fulfilled within the maintenance scope. I'm not saying that it's the case for this Mexican requirement, I'm just saying there is this possibility, generally.
My personal recommendation: get your local Mexico people to be closer to the SAP Mexico team. They are usually responsible to publish information about such local requirements and the SAP release plan.
Hope that helps.
Best,
Henrique.

End of SAP support for EP6

Hi,
Can anyone tell me when SAP plan to end support for EP6?
Thanks,
Paul

As per [PAM|https://service.sap.com/pam] for SAP NetWeaver 04 its as follows:-
End of mainstream maintenance 31.03.2010
End of extended maintenance 31.03.2013
*Chintan

SAP Support for Pay Service?

A friend would like me to find out on this site for him:
Is there any service on this site or anywhere, that he can get support, even if it costs some money?
Basically he has a new BW job and he fears he may encounter a problem and would like to deal with it without showing his ignorance to his employer.
Sure, he has been researching on this site but sometimes it may be too specific that he may want o speak with someone on the phone or chat.
Is there any service here or out there, like that?
Thanks.

Thanks and that makes sense in the absence of an actual SAP BW support service.
Almost all products out there, Linux, NT, 2000, Netware, have those type of services so we thought there will be one out there for SAP BW.
The point is that, in a critical situation, one would like to quickly be assured of a guaranteed response instead of posting and hoping for a response on a forum, such as this.
I will leave the case open and see if others may be aware of any SAP BW support services on the market.
Thanks.

SAP Support for ITS version iViews on ESS

Hi All,
I heard that SAP will not be supporting all the transactions on Poratl used in ITS version from 2009 onwards. Is that true ?
Pls let me know ...!
Any support doc for this statement ?
Reagards
Vijay

Vijay,
What version of ITS are you referring to ? Standalone 6.20 or Integrated ITS?
Some transactions will probably not be supported as the integrated ITS has some limitations due to weblogic.
Ronald

SAP Support for ISR Framework for MSS

Hi,
Does anyone know if SAP will continue supporting the JSP forms developed using old MSS. I know they are supported in ECC 6.0 but going forward will SAP continue to support JSP forms or should we start doing the new development in Adobe forms (would prefer JSP)
Thanks
Salim

since no one replied to this questions I am closing the thread. BTW, this is what I have found out from another thread...
The 2005 PCR iviews are written in WebDynpro, and appear to assume that each one will be an Adobe form!
If old PCR iviews are assigned to the manager (give them the old MSS role under Migrated Content->EP5.0... in the pcd if you have it installed), you will be able to create a PCR with the JSP forms (regardless of the "Entry in Web" setting in QISRSCENARIO).
Hope this helps.
Thanks
Salim

SAP Support for Data Archiving

Hello,
We just wanted to confirm if SAP will support issues if we encounter issues while restoring data archived via SARA. For example, if in the process of restoring archived data a defect is found, is this still supported by SAP?

Hi
Supported and the SAP Data Archiving Support Tools are SARA , DART and SARI
SARA --- SAP Archive Administration
All data archiving activities commence with Archive administration (transaction SARA). SARA provides the overall administration of archiving schedules and manages the archiving sessions. The process includes customization of objects, their conversion to archived sequential archived files and most importantly, their overall management. In addition to these, the archive administration process also retrieves the archived files and converts the data through an automated process, if there is a change in software, hardware or the data structure. The data archiving process is streamlined and simplified through the Central command of archiving administration
DART --- Data Retention Tool
A data retention strategy is required for retaining enterprise information for long periods of time. The Data Retention Tool (DART) provides this functionality. It is capable of extracting data, which is period-specific as well as any supporting information. DART transforms database objects into flat files that can be read by any third-party software designed for flat files. It is available as an add-on for older versions of SAP R/3, but is an integrated feature of the recent versions of SAP R/3.
SARI --- SAP Archive Information System
SARI provides much-needed retrieval capabilities against previously archived data. It requires the archive files be loaded into new tables in the database. In this approach, AS requires detailed, technical knowledge of the database table structure and field layouts. Database structure of an enterprise needs to be flexible and dynamic to be able to quickly adapt to organisational changes. It might happen that the current database structure is not compatible with the structure of database when archive files were initially generated. Archive Information System is a standard tool delivered by SAP that facilitates customized access to the archived data
Regards
Venkat

SAP Support for Classic G/L in ECC 6.0 and above

Similar Messages

Maybe you are looking for