GRC AC5.3 CUP Requests Transaction Data Migration to 10.1
Hi,
We are starting a new upgrade from AC5.3 to AC 10.1 project. In migration document it mentioned that we can migrate CUP requests transactional data to 10.1.
our management is asking to maintain the CUP transaction data in AC10.1 application for future reference for auditing requirements. After closing of all old CUP requests we need to migrate CUP Requests Data into 10.1.
Is it possible? If possible, Please let me know if there are any challenges from your experience from your upgrade projects of same requirement.
Thanks,
Sathish.
Hi Ram,
Good Day,
Is that possible to download old CUP request as PDF format in AC 10.1 as part of data migration
Regards
Narayanan
Similar Messages
-
Legacy transaction data migration for Shopping cart
Dear SAP Gurus,
We have client rquirenment to migrate all the Legacy transaction data to SRM shopping cart (SRM 7.0),
kindly suggest for the same.
Regards,
Vinod
Edited by: Vinod Malagi on Jul 16, 2010 11:44 AMHi Vinod,
Depending on the documents you wish to transfer there may be several ways that they can achieve this.
1. Set up middleware to map your legacy format to SRM format then call BAPI (SRM) to create the documents (this is a consulting project).
2. Use the (purchasing documents) upload/download functionalities provided by SRM. The upload/download functionalities support Excel tab-delimited format. You have to ensure that you conform to this file structure. You can get more information about this at http://help.sap. com/saphelp_srm2007/helpdata/en/45/f725350ce02312e10000000a11466f/frames et.htm .
Whatever you wish to do here amounts to an "integration project" which requires a consulting solution which is why you would not find a document clearly outlining how to do it. Hope that helps.
Kind Regards,
Lisa -
Is there a "best practice" for transaction data conversions from a legacy system into R/3? I am in a project where I have to create a strategy for SCM transaction data (PO's, Inventory, Vendor Invoices, and so on). I would like to know the pros and cons of migrating a PO in their various stages (Open, G/R but not yet invoiced, Partial G/R). Basically a strategy to propose to my client regarding their SCM transaction data.
Thanks for your help!!!!hi,
For uploading the GLs :-->
Use FB50 entry Dr GL a/c Credit Data migration a/c or controlling a/c
For uploading the Vendor balances : -->
Use FB60 entry Dr Data migration a/c or controlling a/c and credit Vendor a/c (individually)
For uploading the Customers balances :-->
Use FB70 entry Dr Customers a/c (individually) Cr Data migration a/c or controlling a/c
For uploading the Assets-->
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (invidiually) Cr Data Migration account or controlling account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero.
For posting the transactional data use LSMW for relevant TCODES
Radha -
Error in creating CUP request on GRC AC 5.3 SP12
-- Request dump for Action Path is scrTopNav.cfg
2010-09-27 20:14:00,416 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@541:logRequest() : initTabName:0::config_request_type#
2010-09-27 20:14:00,416 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@546:logRequest() : -- End Request dump for Action Path is scrTopNav.cfg
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCreateRequest| Screen: |scrRequestDetails|
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@105:execute() : Module#AE#Conversation#cnvCreateRequest#Screen#scrTopNav#Action#cfg#
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@248:execute() : Changing Screen: FROM: scrRequestDetails TO scrTopNav
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.actions.SuccessAction
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@296:execute() : Target returned by execute action: success
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@458:service() : forwarding to:CFG.cnvConfigRequest.scrConfigRequest.loadConfigRequest.do
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@521:logRequest() :
-- Request dump for Action Path is CFG.cnvConfigRequest.scrConfigRequest.loadConfigRequest
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@541:logRequest() : initTabName:0::config_request_type#
2010-09-27 20:14:00,417 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@546:logRequest() : -- End Request dump for Action Path is CFG.cnvConfigRequest.scrConfigRequest.loadConfigRequest
2010-09-27 20:14:00,418 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCreateRequest| Screen: |scrTopNav|
2010-09-27 20:14:00,418 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@105:execute() : Module#CFG#Conversation#cnvConfigRequest#Screen#scrConfigRequest#Action#loadConfigRequest#
2010-09-27 20:14:00,418 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@209:execute() : Changing Module: FROM: AE TO CFG
2010-09-27 20:14:00,418 [SAPEngine_Application_Thread[impl:3]_13] DEBUG Context.java@259:clearConversationRep() : INTO the method
2010-09-27 20:14:00,418 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.configuration.actions.RequestConfigAction
2010-09-27 20:14:00,421 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : ,list size=17
2010-09-27 20:14:00,421 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #0# element:com.virsa.ae.dao.dto.RequestTypeDTO@50e750e7[reqType=NEW_HIRE,reqDesc=New Hire,workflowType=AE,isDeletable=true,shortDesc=New Hire,locale=1,endUserLongDesc=New Hire,active=1,sequenceOrder=0,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #1# element:com.virsa.ae.dao.dto.RequestTypeDTO@51935193[reqType=CHANGE,reqDesc=Changes to an Existing Account,workflowType=AE,isDeletable=true,shortDesc=Change Account,locale=1,endUserLongDesc=You can request changes to existing account using this link. You can request additional access and other changes to an account such as account validity and so on,active=1,sequenceOrder=1,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #2# element:com.virsa.ae.dao.dto.RequestTypeDTO@52165216[reqType=DELETE,reqDesc=Account Deletions,workflowType=AE,isDeletable=true,shortDesc=Delete Account,locale=1,endUserLongDesc=You can use this link to request deletion of accounts from various systems. You can also request mass deletion of accounts,active=1,sequenceOrder=2,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #3# element:com.virsa.ae.dao.dto.RequestTypeDTO@533c533c[reqType=INFORMATION,reqDesc=Information,workflowType=AE,isDeletable=true,shortDesc=Information,locale=1,endUserLongDesc=Does not know which link to select from above? Click this link for information about what access you need,active=1,sequenceOrder=3,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #4# element:com.virsa.ae.dao.dto.RequestTypeDTO@54005400[reqType=LOCK,reqDesc=Locking Accounts,workflowType=AE,isDeletable=true,shortDesc=Lock Account,locale=1,endUserLongDesc=You can use this link to request locking of accounts in various systems. You can also request mass locking of accounts,active=1,sequenceOrder=4,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #5# element:com.virsa.ae.dao.dto.RequestTypeDTO@55095509[reqType=NEW,reqDesc=New Account,workflowType=AE,isDeletable=true,shortDesc=New Account,locale=1,endUserLongDesc=Use this link to request new accounts and Roles/Responsibilities/Structural Profiles,active=1,sequenceOrder=5,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #6# element:com.virsa.ae.dao.dto.RequestTypeDTO@55c955c9[reqType=UNLOCK,reqDesc=Unlocking Accounts,workflowType=AE,isDeletable=true,shortDesc=Unlock Account,locale=1,endUserLongDesc=You can use link to request unlocking of accounts. You can also request mass unlocking of accounts,active=1,sequenceOrder=6,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #7# element:com.virsa.ae.dao.dto.RequestTypeDTO@56995699[reqType=SUPER_USER_ACCESS,reqDesc=Superuser Access,workflowType=AE,isDeletable=true,shortDesc=Superuser Access,locale=1,endUserLongDesc=You can use a link to request Superuser Access,active=1,sequenceOrder=7,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #8# element:com.virsa.ae.dao.dto.RequestTypeDTO@56fe56fe[reqType=MITICTRLC,reqDesc=Create Mitigation Control,workflowType=MITICTRL,isDeletable=true,shortDesc=Create Miti. Ctrl.,locale=1,endUserLongDesc=Create Mitigation Control,active=1,sequenceOrder=8,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #9# element:com.virsa.ae.dao.dto.RequestTypeDTO@57d657d6[reqType=MITICTRLD,reqDesc=Delete Mitigation Control,workflowType=MITICTRL,isDeletable=true,shortDesc=Delete Miti. Ctrl.,locale=1,endUserLongDesc=Delete Mitigation Control,active=1,sequenceOrder=9,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #10# element:com.virsa.ae.dao.dto.RequestTypeDTO@591f591f[reqType=MITICTRLU,reqDesc=Update Mitigation Control,workflowType=MITICTRL,isDeletable=true,shortDesc=Update Miti. Ctrl.,locale=1,endUserLongDesc=Update Mitigation Control,active=1,sequenceOrder=10,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #11# element:com.virsa.ae.dao.dto.RequestTypeDTO@59825982[reqType=MITIOBJC,reqDesc=Create Mitigation Object,workflowType=MITIOBJ,isDeletable=true,shortDesc=Create Miti. Obj.,locale=1,endUserLongDesc=Create Mitigation Object,active=1,sequenceOrder=11,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #12# element:com.virsa.ae.dao.dto.RequestTypeDTO@5a375a37[reqType=MITIOBJD,reqDesc=Delete Mitigation Object,workflowType=MITIOBJ,isDeletable=true,shortDesc=Delete Miti. Obj.,locale=1,endUserLongDesc=Delete Mitigation Object,active=1,sequenceOrder=12,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #13# element:com.virsa.ae.dao.dto.RequestTypeDTO@5b6a5b6a[reqType=MITIOBJU,reqDesc=Update Mitigation Object,workflowType=MITIOBJ,isDeletable=true,shortDesc=Update Miti. Obj.,locale=1,endUserLongDesc=Update Mitigation Object,active=1,sequenceOrder=13,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #14# element:com.virsa.ae.dao.dto.RequestTypeDTO@5bca5bca[reqType=RISKC,reqDesc=Create Risk,workflowType=RISK,isDeletable=true,shortDesc=Create Risk,locale=1,endUserLongDesc=Create Risk,active=1,sequenceOrder=14,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #15# element:com.virsa.ae.dao.dto.RequestTypeDTO@5cca5cca[reqType=RISKD,reqDesc=Delete Risk,workflowType=RISK,isDeletable=true,shortDesc=Delete Risk,locale=1,endUserLongDesc=Delete Risk,active=1,sequenceOrder=15,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,422 [SAPEngine_Application_Thread[impl:3]_13] DEBUG com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll() : : #16# element:com.virsa.ae.dao.dto.RequestTypeDTO@5dc95dc9[reqType=RISKU,reqDesc=Update Risk,workflowType=RISK,isDeletable=true,shortDesc=Update Risk,locale=1,endUserLongDesc=Update Risk,active=1,sequenceOrder=16,actType=<null>,actDesc=<null>,actSeq=0,actionMap=<null>]
2010-09-27 20:14:00,423 [SAPEngine_Application_Thread[impl:3]_13] INFO com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll : : going to return no of records= 17
2010-09-27 20:14:00,424 [SAPEngine_Application_Thread[impl:3]_13] DEBUG NavigationEngine.java@296:execute() : Target returned by execute action: success
2010-09-27 20:14:00,424 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AEFrameworkServlet.java@458:service() : forwarding to:/cfg_request.jsp
2010-09-27 20:14:00,426 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,426 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AECacheUtil.java@2085:getAllActiveWorkFlowTypeDropDown() : INTO the method : pLocaleId1
2010-09-27 20:14:00,426 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,426 [SAPEngine_Application_Thread[impl:3]_13] DEBUG AECacheUtil.java@2085:getAllActiveWorkFlowTypeDropDown() : INTO the method : pLocaleId1
2010-09-27 20:14:00,426 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,427 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,427 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,427 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,428 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,428 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,429 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,429 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,429 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,429 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,430 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,430 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,430 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,430 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,431 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,431 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:00,431 [SAPEngine_Application_Thread[impl:3]_13] DEBUG LocaleUtil.java@321:getUserLocaleId() : intLocale : 1
2010-09-27 20:14:05,472 [SAPEngine_Application_Thread[impl:3]_18] DEBUG AEFrameworkServlet.java@521:logRequest() :
What is the problem guys???Hi,
Your error message is too small to get information for troubleshooting!!
Please search the [SAP Service Market Place for SAP Notes|http://service.sap.com/notes] with a filter on Application Area field with GRC AC CUP (you can browse to select).
Regards,
Dipanjan -
Role created in ERM is not appearing in CUP request for assignment-GRC 10.0
Hi,
We are on GRC 10.0 - SP5
We have created a role in ERM and it was succesfully created in backend system. However when we tried to assign the same role using CUP request - the role is not appearing.
1) Do we need to upload roles for CUP in GRC 10.0 (similar to 5.3) to populate. Will the role doesnot automatically appears in GRC database for CUP as it is created through ERM?
2) If the roles are imported in ERM with role owner information, does the same reflects for CUP also for role owner approver assignments?
Thanks and Best Regards,
Srihari.KHi Sri,
Is the role status set to "production" ??
Cheers,
Diego. -
Billing Legacy master & transactional data conversion/migration in SAP ISU
Hi Experts,
Please let me know, in ISU implementation project, what is Billing related Legacy master & transactional data conversion/migration is done in SAP ISU system.
Thanks in advancePankaj,
There is no straight forward transaction to download the Configuration data and export it to a file.
However, you can use the BC set functionality to extract the IMG node with its contents.
Check the following SAP help portal link for more info on BC sets
Business Configuration Sets (BC-CUS) - SAP Library
The archive data that you are talking about; Is it master data or transaction data?
Also, what this data is related to-Financial Documents, Billing related info?
There is one standard transaction SARA through which based on the migration object you can archive the data and export it into a file in a particular location..
Hope it helps..
Thanks,
AB -
GRC-AC v5.3, patch8.1: cannot retrieve user information in CUP Request
Hello,
version: GRC-AC v5.3, patch8.1
I am currently having trouble bringing up user information in a CUP Request. It is only occuring in our GRC-AC DEV system. I have checked that all of my AE Config settings are the same and the backend system RTA is correct.
Thanks for your help!
Here is the AE Log:
2009-12-02 14:21:48,912 [SAPEngine_Application_Thread[impl:3]_35] ERROR com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
at com.virsa.ae.service.sap.SAPR3UserDAO.executeFind(SAPR3UserDAO.java:441)
at com.virsa.ae.service.sap.SAPR3UserDAO.getUsers(SAPR3UserDAO.java:1762)
at com.virsa.ae.service.umi.sap.SAPR3SearchUser.getUsers(SAPR3SearchUser.java:317)
at com.virsa.ae.search.bo.SearchUserBO.findUsers(SearchUserBO.java:110)
at com.virsa.ae.search.actions.SearchUserAction.searchUsers(SearchUserAction.java:2315)
at com.virsa.ae.search.actions.SearchUserAction.searchRequestors(SearchUserAction.java:1999)
at com.virsa.ae.search.actions.SearchUserAction.execute(SearchUserAction.java:260)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
2009-12-02 14:21:48,931 [SAPEngine_Application_Thread[impl:3]_35] ERROR Search could not be completed
com.virsa.ae.service.ServiceException: No more storage space available for extending an internal table.
at com.virsa.ae.service.sap.SAPR3UserDAO.executeFind(SAPR3UserDAO.java:444)
at com.virsa.ae.service.sap.SAPR3UserDAO.getUsers(SAPR3UserDAO.java:1762)
at com.virsa.ae.service.umi.sap.SAPR3SearchUser.getUsers(SAPR3SearchUser.java:317)
at com.virsa.ae.search.bo.SearchUserBO.findUsers(SearchUserBO.java:110)
at com.virsa.ae.search.actions.SearchUserAction.searchUsers(SearchUserAction.java:2315)
at com.virsa.ae.search.actions.SearchUserAction.searchRequestors(SearchUserAction.java:1999)
at com.virsa.ae.search.actions.SearchUserAction.execute(SearchUserAction.java:260)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
at com.virsa.ae.service.sap.SAPR3UserDAO.executeFind(SAPR3UserDAO.java:441)
... 23 more
2009-12-02 14:21:48,937 [SAPEngine_Application_Thread[impl:3]_35] ERROR Search could not be completed
com.virsa.ae.service.umi.UMIException: Search could not be completed
at com.virsa.ae.service.umi.sap.SAPR3SearchUser.getUsers(SAPR3SearchUser.java:326)
at com.virsa.ae.search.bo.SearchUserBO.findUsers(SearchUserBO.java:110)
at com.virsa.ae.search.actions.SearchUserAction.searchUsers(SearchUserAction.java:2315)
at com.virsa.ae.search.actions.SearchUserAction.searchRequestors(SearchUserAction.java:1999)
at com.virsa.ae.search.actions.SearchUserAction.execute(SearchUserAction.java:260)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.virsa.ae.service.ServiceException: No more storage space available for extending an internal table.
at com.virsa.ae.service.sap.SAPR3UserDAO.executeFind(SAPR3UserDAO.java:444)
at com.virsa.ae.service.sap.SAPR3UserDAO.getUsers(SAPR3UserDAO.java:1762)
at com.virsa.ae.service.umi.sap.SAPR3SearchUser.getUsers(SAPR3SearchUser.java:317)
... 21 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417)
at com.virsa.ae.service.sap.SAPR3UserDAO.executeFind(SAPR3UserDAO.java:441)
... 23 more
2009-12-02 14:21:48,943 [SAPEngine_Application_Thread[impl:3]_35] ERROR Error in Searching Users...
com.virsa.ae.core.BOException: Error in Searching Users...
at com.virsa.ae.search.bo.SearchUserBO.findUsers(SearchUserBO.java:125)
at com.virsa.ae.search.actions.SearchUserAction.searchUsers(SearchUserAction.java:2315)
at com.virsa.ae.search.actions.SearchUserAction.searchRequestors(SearchUserAction.java:1999)
at com.virsa.ae.search.actions.SearchUserAction.execute(SearchUserAction.java:260)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)Hi,
As per error log, sounds space issue.
"ERROR com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table. com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: No more storage space available for extending an internal table."
Check the tablespace with your Basis guy and increase it if neccessary.
Regards,
Sabita -
Add Fields in CUP Request - SAP GRC Access Control 5.3
Dear Friends,
I am wondering on how to add fields value in CUP (Compliant User Provisioning) SAP GRC AC 5.3.
Currently i'm leading 9 SAP Security Coordinators in Indonesia and i want to create Performance Metrics on how long the CUP Requests is processed. It needs to enhance the CUP by adding value Delegation of Authority and the record no. of the DOA requests.
Really appreciate your inputs on how to add fields value in CUP.
Thank you so much
-Mesti-
Edited by: AnnisaPramesti on Jan 2, 2012 5:37 PMHi.
Check under http://service.sap.com/instguides
SAP BusinessObjects -> SAP BusinessObjects Governance, Risk, Compliance (GRC) -> Access Control -> SAP GRC Access Control 5.3
Cheers,
Diego. -
Migration of Transaction Data from SRM 4.0 to SRM 7.0
Hi
We are upgrading from SRM 4.0 to SRM7.0.
In our old release, many Shopping Cart woul be in the status of Approved, Awaiting Approval and Held. When the same data is migrated to the SRM 7.0 Productive system, how should we take care of the same. We would continue to use the Old Workflow (Application controlled) in SRM 7.0. However we have made changes to the Workflow steps in the new system.
Alo while moving to the new SRM 7.0 Production system, how should we manage the Transactonal Data migration overall.
The client has not agreed to close the Open SC, PO or the confirmations.
Any inputs relating to the Transactional data approach would be highly appreciated.
Regards
RajHi Masa
All said and done we have lot of issues with regard to the data migration. The issues are as below:
1. The POWL doesn't reflect the old data at all in the Upgraded system. I was expecting the "Check Status" functionality to be integrated with POWL so that all the existing Shopping Cart and Purchaser Orders could be seen and the follow on actions could be taken.
2. I am not able to do a generic search on "Advanced Search". For example if I try to Search on the old Shopping Carts, until and unless I give the specific Shopping Cart number, the Search doesn't yield any output.
3. Since POWL doesn't reflect the exisitng Shopping Cart we are not able to proceed ahead with them to create the Follow On documents like Confirmation.
4. The Work Flow in the new system remains Application Controlled only. However we have added few extra steps. The existing "Awaiting Approval" Shopping Carts is not picking up the workflow correctly in the new system.
Any ideas about the same?
Regards
Raj -
What tables contain data for the CUP requests in 5.3?
What are all of the tables that contain the data that appears in the CUP requests? We are on version 5.3 SP13.
We are selling off one of the divisions of our company and one of the terms is that we have to provide all relevant data, including CUP requests. Since there are several hundreds of requests for this division (last count was over 600), it is not practical to just download the individual requests out of CUP. So plan B is to just give them the data.
I know there are several tables that contain this data, and I know some of them (such as VIRSA_AE_REQD_HDR and VIRSA_AE_RQD_WPHS), but I don't know all of them. (and I would rather not have go thru and to check every table)
Thanks.Hi Bob,
I have never looked at the VT_AE tables to extract any information. Since your requirement is unique, I have a positive note that SAP would help you with it. Giving a try would worth it sometimes
Else, paste the list of tables here, so that some one can help you.
Have a great weekend!!
Cheers,
Raghu -
Transaction and open item data migration
Respected Gurus,
we are implememting first time sap to one company in ecc 6.0,how can i migrate the financial data,(openitems and transaction data)what is the procedure.
regards
janaHi Janardhan,
For all FI transactional data (in this I include open AR items, open AP items, GL balances and perhaps even GL at an item level) by the far best method, especially if you are new to this, it to extract the data from the legacy system into a text file, load and format the text file using LSMW, from LSMW call the standard load program RFBIBL00.
When you choose RFBIBL00 as the load method it will tell you that this is a direct upload program which is not strictly true. When you run the RFBIBL00 step you will be able to choose between direct upload and batch upload. Choose the batch method as it is more transparent, unless your volumes are huge.
We will shortly be posting some load guides for finance migration on our website research page.
Good luck,
Ben
http://www.harlex-ltd.com -
Requesting advice on how to initialize (delete) APO transaction data
Hello experts,
We are working on a project to implement a "clean", master-data-only APO system. The APO system is to be created by doing a full backup of an existing APO system and restore as a new instance (then BDLS to change the system ID).
My question involves the removal of all transaction data (purchase orders, released production orders, sales orders, purchase requisitions, etc) from the new APO system. We've tested several delete programs to try to remove these documents from APO (/SAPAPO/DELETE_PP_ORDER, /SAPAPO/RLCDELETE, /SAPAPO/SDRQCR21, /SAPAPO/SDORDER_DEL, /SAPAPO/OM_DELETE_INCON_ORDERS to name a few) with limited success.
Instead of removing these documents individually is it possible to simply re-initialize APO so that all transaction data is removed but all master data (PPMs, locations, products, transportation lanes, rules, etc) is kept intact?
Any advice is greatly appreciated.
Regards,
David Eady
Application Delivery Team Lead
Propex, IncHi David,
If you find the comprehensive solution, let me know!
I have had best luck with deactivating ALL IMs, then running CCR and deleting all marked as no active model. Then run the programs mentioned in your posting, as well as anything designed to make data 'consistant'. After that, there are usually some aggravating bits that don't want to go away, which I have had to chase down and delete manually. It is a tedious process, one that usually takes me a couple of days.
Regards,
DB49 -
Data Migration from Legacy System in CRM
Hi All,
We are going to Implement a new CRM project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of CRM and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Active Campaigns/Campaign Content/Dispositions
4. Contacts
5. Contracts
6. Opportunities
7. Payment Arrangement History
8. Payments
9. Premises
10. Rate Changes
11. Security Deposits
12. Business Partner Relationships
13. Web self-service information
14. Usage that has been used for quotes
15. Tax history information, including AXCIS
17. Service Requests
18. Service Order History
19. Security Deposits
20. Reference Values
21. Rate Changes
Can anybody please tell any transaction code in CRM where can I find the Data migration for the above objects is possible or not.
Thanks in Advance,
Sai.Hello,
for migration into CRM I would suggest the 'XIF-Interfaces'; these are interfaces provided in CRM for connection to external systems. I'm not sure if this will cover all objects mentioned above, but at least some of them should exist.
Some information about existing interfaces can be found in the integration repository under http://ifr.sap.com/index.html; from the start screen first select 'Enter the repository' and then have a look under 'generic components' and 'SAP CRM'.
Regards, Katja Ohliger -
Data migration ALE or idocs and bapis
hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada -
Data migration from ECC5.0 to ECC6.0
Hi All,
Is there a standard SAP utility to migrate the data from ECC5.0 to ECC6.0? Assumption is that all the standard fields and the transactions are same. Good example for this case is standard material master, Purchase order, purchase info record etc.
Currently I am planning to extract the data from source system (using custom program or table download etc...) and upload the data into target system (using LSMW, eCATT, BDC etc...).
Is there a standard way to load the data into target system without extraction and upload? Please let me know.
Thanks
NagarajanALE Customizing
1) IMG > Application Link Enabling (ALE) > Sending and Receiving > logical systems > Define Logical System: name it XXXXXX
2) IMG > Application Link Enabling (ALE) > Sending and Receiving > Systems in Network > Asynchronous Processing > Assigning Ports > Define Port: name it XXXXXX Description: Files for Migration to YYY
The port need to be defined beneath FILE
The IDOC record types for SAP Release 4.x need to be selected
A physical directory is needed. One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
3) IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
a) Cross-System Company Codes
b) Assign Cross-System Company Code to Chart of Accounts
c) Assign Company Code to Cross-System Company Code
Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
4) IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
Here we need a distribution model
Structure: model view (call it XXXXXX)
Sending system (AAAAAA)
Receiving system (XXXXXX)
5) IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
(Beside of customers and vendors, we need to add the message type BOMMAT for material bill of materials and MATMAS for material master to to the distribution model, probably manually in step 4. Depending on further requests for automatic migration the one or other message type may need to be added later )
6) IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
Partner profile type/Partner type: LS logical system
Partner profile/Partner number: XXXXXX
Details at Post Processing agent
Typ: US user
Agent: JJJJJ
Lang: EN
Outbound parameters
Message type: ADDR2MAS
ADR3MAS
ADRMAS
MATMAS
CREMAS
DEBMAS
Details per message type like this:
Receiver port: XXXXXXX Output mode: Collect Idocs and Do not start subsystem
IDOC type: for ADDR2MAS use ADR2MAS02
ADR3MAS ADR3MAS02
ADRMAS ADRMAS02
MATMAS MATMAS03
CREMAS CREMAS03
DEBMAS DEBMAS05
Activate syntax check
7) Authorization needed to execute Transactions:
BD12 Send Customers
BD14 Send vendors
BD10 Send material
BD30 Send bill of material
Depending on future migration requests for other objects we may need some more.
Maybe you are looking for
-
A while back my early model iPod died and I have no desire or money to replace it. I invested a small fortune in my library and it was quite a blow when my pc died eventually as well. I still have the old broken ipod, (good for it's serial number bu
-
(10.8) Finder.app does not update file lists and Dropbox stops syncing, could they be related?
The Finder on three identical, brand new, iMacs does not refresh when new files are added or removed from a folder. They were all purchased about a month before the release of Mountain Lion and were upgraded upon release. The problem is intermittent,
-
How do i turn off location service while using facetimeq
I cannot see the topic in location service to turn it off in setting please help
-
Can anyone help - LR5.3 won't start after only 2 successful days!!
2 days ago installed LR5.3 trial on my new PC bought to run LR and CS6 - Win 7 Pro, Xeon E3-1230, 32gb memory, SSDs etc (the works). Worked great for 2 days, cataloging a big trip, lots of adjustments made. Yesterday I found LR had unexplained errors
-
Anyone have kde 3.5.10 compiled? ..last i found is out date and not work. Kde 4.3.* is too bug ..and not usable for daily work. Please not suggest have to use gnome or other ..i search kde 3.5.10 (and wait kde 4.5) If not ..for you is possible make m