Working with badi in SAP ECC 6.0

i had like to know whether the creation of badi is different in ECC 6.0 is difffeerent than the earlier versions of sap.what is enhancement spot.

Sure:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/the%2bnew%2benhancement%2bframework%2band%2bthe%2bnew%2bkernel-based%2bbadi
Regards,
John.

Similar Messages

Reg: Replacing i-way with PI for SAP ECC 6.0 version

Hello Experts
currently we are using R/3 4.7 version and middle ware we are using is i-way and we are planning to upgrade to ECC 6.0 and i would like to know how compatible is i-way is with SAP ECC 6.0 and is there any neccessity to replace the same with PI.
and currently we are using RFC as a method of communication between R/3 and i-way and in future i don't want to change the existing coding , is it feasible to use PI via RFC.
As i am ABAPer, i am new to this PI and please let me the know the risks involved and it is viability.
Thanks and Regards
S.Janagar

Hi Gavin,
you should always use the SQL EE for SAP installations (because of additional features that only come with EE).
Concerning SQL 9 or SQL 10, I would definitely go for SQL 10. It has some nice features like Backup Compression, Page/Row Compression and so on. Have a look [here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a236a2-8104-2b10-5ebe-8fef61cc82fd]. Just make sure that your installation meets the SR3 requirements.
We already have SQL 10 in production and did not encounter any problems.
Regards,
Sven

How to map the Categorization Reasons (SAP CRM) with Order Reason (SAP ECC)

Hi Team .
I have created a service order for a spare parts material in CRM Web ui , order got saved successfully without errors and had replicated to ECC system.
Issue : When the user is processing for billing, the system is asking for the order reasons to enter for the Item . (Checked the order in the incompletion log in of ECC) . Though we have maintained the categorizations in the CRM System.
The order reasons in the SD (ECC) and categorizations in the CRM are same.
Client requirement: The order created in CRM by mentioning the categorization reasons should automatically replicate to the ECC system without deviation and billing should happen in ECC without asking the order reasons.
Note # Order reasons cannot be removed from the ECC System
Regards,
VCS

Dear Team,
I had resolved the issue on my own .
Sol : We had made the Order reasons mandatory in the CRM Web UI service order and we had removed the Incompletion Log for that particualr transactions types from the SD.
Regards,
VCS

Modify fields on screen with BAdI?

Hi,
I want to modify/customize a screen (Shopping Cart in SRM) in a way that some fields are displayed, others not. Some people told me that this might be possible using a BAdI. As I have never worked with BAdI technology before, I hope that somebody here can help me a bit.
- Where do I get good documentation on BAdIs?
- Are there any pre-defined BAdIs for modifying screens or would I have to create a new one?
In advance, thanks a lot for your help!
Regards,
Verena

Hello Verena,
To look for list of Badi, run transaction SE18. Then enter '*' with the dropdown. You can search Badis by the application hierarchy or by Badi name/description. Once you found the correct Badi, run transaction SE19 to create an implementation of the Badi you found using SE18. Are these sound familiar? Yes, SE18 is like transaction SMOD while SE19 is like CMOD in the User exit. Badi is replacing User exit-ie new enhancement developed by SAP should be in terms of Badi. However, this does not means old User exits going away. You still can use user exits provided by SAP.
So when you are searching for enhancement that you can use to intercept SAP standard program, you can search by Badi (SE18) or User exit (SMOD).
Badi or User exit are delivered by SAP for giving customer an opportunities to change a little bit the standard way SAP process. You can't simple create a new BADI, it has to be delivered by SAP. You can implement a Badi given by SAP.

DS 3.2 u201CDirect Downloadu201D from SAP ECC Dump RFC_ATTACH_GUI_FAILED

DS 3.2 u201CDirect Downloadu201D from SAP ECC Dump RFC_ATTACH_GUI_FAILED - Start 'sapgui' failed
We are running DS 3.2.1 with a data source connected to ECC 6.0 using u201CDirect Downloadu201D.
DS 3.2 Designer on Windows, DS Job server on Unix, SAP ECC running on Unix (different Unix box than DS).
We get a dump in the SAP ECC source system, RFC_ATTACH_GUI_FAILED Start 'sapgui' failed.
DETAILS
From the DS Designer
-     We can view the data in the SAP ECC T001 table from the ECC Data Source.
-     Run the job from the DS designer on the DS Unix server, jobs starts the ABAP Data flow, then gets the error:
>Cannot connect to SAP Applications datastore <DS_JR_ERD100_TEST> using host <ierpt1>, client <100>, user <G6992JR>, and system number <27: CRFC error: Start 'sapgui' failed.>. Please make sure the SAP server is running and the login information is correct.
-     In the SAP ECC source system Tran ST22 I see the following dump:
>Runtime Errors         RFC_ATTACH_GUI_FAILED
>Start 'sapgui' failed.
>u2026
>Call Program........."al_engine"
>Function Module..... "SYSTEM_RFC_VERSION_3_INIT"
>u2026
>Termination occurred in the ABAP program "SAPLSYST" - in "SYSTEM_ATTACH_GUI".
>The main program was "SAPMSSY1 ".
-Data Store to SAP ECC settings:
o     ABAP Execution Option:     Generate and Execute
o     Execute in Background:          No
o     Data Transfer Method:          Direct Download
o     Working dir on Sap server:     ECC Server, no files show here.
o     Local Directory:               DS Server, no files here
o     Generated ABAP Dir:          DS Unix server, the ABAP program is here.
Has anyone seen this issue?
Shouldnu2019t it use WS_DOWNLOAD vs. GUI_DOWNLOAD?

Thanks for the information on the Direct Download.
I will check test by running the generated ABAP in the SAP ECC system to see why we get the GUI ERROR.
I now understand that Direct Download is for testing & small amounts of data & "Old" functionality.
We were doing a test on a table with only 87 records.
We wanted to test that we could connect from DS to the SAP ECC system & that the DS Data Flow worked.
Also, our SAP ECC & our Data Services are on different Unix servers that do NOT have a common directory.
So if we used Shared Directory, the file would be deposited on the SAP Server, but the DS server would not be able to see it to pick it up. So we may have to look at FTP option.
Has anyone used DS to extract from an SAP ECC on a Unix server to Data Services on a DIFFERENT Unix server with no common directory?
We would really prefere NOT to have to create a temporary file, but would rather it worked just like the BW extracts from SAP ECC, it just sends the records over via TRFC's, not temp file, or if it woudl work the same way as when DS pulls from one oracle DB on a Unix server to another oracle DB on a Different Unix server, I don't think that creates temporary files.
Thanks Again for your help
Jay Roble

CRITICAL: Error occured while working with configuring .in WAS deploytool

Hi,
I have installed developer workspace WAS edition SP11.
I had given a master password to all the users created while installation.
But now for deployement and visual administration that password is not working.
So i started deploytool to enable Superadmin.
It allows me to change the value but when i save it,
it throws error stating:
<b>"CRITICAL : Error occured while working with configuration"</b>
and then deploytool stops abruptly.
Unless I enable superadmin, i wont be able to reset all my passwords.
How do i proceed??
AbhiJeet..

Hi all and Abhijeet especially,
have you found the cause of this problem? I'm experiencing exactly the same thing. What's to be done about this?
<u>excerpt from configtool log file:</u>
Error occurred while working with Configuration.
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:294)
     at
     com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1217)
     at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:833)
     at com.sap.engine.configtool.batch.task.TaskUtil.changeProperties(TaskUtil.java:337)
     at com.sap.engine.configtool.batch.task.ChangeServicePropsTask.go(ChangeServicePropsTask.java:59)
     at com.sap.engine.configtool.batch.task.TasksThread.run(TasksThread.java:46)
Caused by: com.sap.dbtech.jdbc.exceptions.BatchUpdateExceptionSapDB: [-3018]: Invalid numeric parameter(input position 2)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.executeBatch(CallableStatementSapDB.java:608)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
     at
     com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execInsertEntryBatch(DBAccessDefault.java:1170)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:257)
     ... 5 more
Message was edited by: Chee Choong Ching

Potcode table report in SAP ECC 6.0

Hi,
we just upgrade our R3 systeem to SAP ECC 6.0 and with this new SAP ECC we can not find the old report for our postcode table check. In previous system, we use the following report to update our postcode table :
- RSADRLSM01
- RSADRLSM02
- RSADRNL_POSTCODE
With SAP ECC 6.0 the latest report (RSADRNL_POSTCODE) in not available and because of that we can not update our postcode table.
Anyone experience the same problem?
Best regards,
Audrey N. Tamara

hi,
I checked this on the systems available to me and the mentioned report RSADRNL_POSTCODE is not available in any release 4.63 and higher, i.e. it isn't available in ECC 600 either.
the NL part suggests to me that this is part of a (Netherlands) country specific extension of any industry solution or it is simply a custom report in SAP's namespace.
So, check if your system's country specific add-ons are in place already or open a customer message to SAP with respect to your country version.
regards,
anton

7373 does it work with Mercedes bluetooth cradle

Hi does anyone know if the 7373 work with the Mercedes SAP Phone cradle. (Bluetooth)
Thanks

It should work but you will need to check with a mercedes dealer for a definate answer.

SAP ECC 6.0 SR3 Cluster failover not working in AIX with DB2 UDB V9.1 FP6

Hi Gurus,
We have installed the SAP ECC 6.0 SR3 High Availability with DB2 UDB V9.1 FP6 in AIX cluster environment.
After installation we are doing the cluster fail test.
Node A
Application Server
Mount Points:
/sapmnt/<SID>
/usr/sap/<SID>
/usr/sap/trans
Node B
Database Server
Mount Points:
/db2//<SID>
The procedure followed to do the cluster failover:
We have down the cluster on Node A and all the resources of the Node A has been moved to Node B.
On Node B when we issued a command to start the SAP. It says u201Cno start profiles foundu201D
WE have down the cluster on Node B and moved the Resource from Node B to Node A . There the db2 User IDu2019s are not available. We have crated the user Idu2019s manually on Node A. however it did not work.
Please suggest the procedure to start the sap in cluster failover.
Best Regards
Sija

Hi Sija,
Can i have detailed scenario in your cluster configuration.
Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
Regards
Nick Loy

SAP ECC 6.0 SR3 Cluster failover not working in windows with DB2 UDB V9.1 F

Dear Expertise,
We have installed the SAP ECC 6.0 SR3 High Availability with DB2 UDB V9.1 FP5 in windows cluster environment.
We have installation following instances on nodes 1 and 2.
Node 1
DB2 database software
Central service instance for ABAP Installation on Shared drive G:
First MCSC node to create a cluster group u201Cpdssapgrpu201D
Database group u201Cpgsdbgrpu201D(Shared Drive)
Enqueue replication service
CI (central instance)(local Drive)
Node 2
DB2 database software
Additional cluster node
Enqueue replication service
DI(dialog instance)(local Drive)
I can login into the system using both CI and DI.
if my SAP Cluster group is moved from one node to another i can still login into the system
But when my DB2 group is moved from node A to node B my SAP services are getting closed
and i am getting the message database not found
so please Guide me as soon as possible Friends.
Thanks and Regards,
Ravindra
Edited by: Ravindra Bade on Mar 6, 2009 10:22 AM

Hi Ravidra
Have u solved the probelm I also have the same problem when i move the groups from node1 to node2 manually my 2 servrces 00 and 01 are failed not able to bring up again. If You solve the problem please guide me the solution to solve this.
THanks in advance

SAP PI FTP sender adapter not working with SAP ECC over Itanium

Hi,
We have been running normally SAP PI 7.0 SP14 with no issue for a while.
We are now in the process of migrate the SAP ECC system from PA risc to IA platform. We are performing some tests between SAP PI and SAP ECC to check that the platform migration is not affecting us in any way and we have found that FTP adapter sender is not working anymore (receiver is working as usual).
We place some files in the new ECC system and when PI goes to retreive the files it is like it can not read anything. It gives no error but it does not pick any file. This is not happening with the old platform.
Does anyone have any idea?
Thanks a lot for your help
Diana

Hi,
I am using FTP connection and for the receiver it is working fine.
Thanks
Diana

Integrate with a vendor from SAP ECC 6.0 for 'PunchOut' functionality

Hi Friends,
Pardon me if I have made mistakes in using the terminology in my posting. We just use SAP ECC 6.0 and no SRM. We want to integrate with a vendor for so-called Punchout. Our users will click a URL link from our Intranet and it takes them to Vendor's catalog website. They can choose items and create a shopping cart. The website will return us a unique Shopping Cart ID with list of Items in cxml format. We can use that information and create PO. We are not familiar with cxml format and how to process the PO. Is this a standard functionality in SRM ? I don't think we can install SRM since we don't have Business suite license. If any one has experience with above scenario, ie connecting to vendor's cataglog from SAP ECC 6.00 without SRM, can you pl share with us ?
Niranjan

Hi Masa
Thanks for the reply. The vendor supports OCI as well. However, since I was not familiar with it, I was thinking to go with cXML. When I opened the OCI pdf in the URL that you mentioned, it talks about SRM server. Like I had mentioned earlier, we don't use SRM at our company here. Can you let me know in couple of steps how OCI works and how fast we can implement in our ERP ECC 6.0 environment ? I am delighted to note that one of the companies in Japan implemented in 4 hours.
Thanks for your help,
Niranjan

** The XML output file is unreadable in SAP ECC 6.0 (Working fine in 4.6c)

Hi Friends,
I am working in SAP Technical upgrade Project from 4.6C to SAP ECC 6.0. In 4.6c one Z program is there, the output of Z program is to generate output XML file in the application Server. We checked and downloaded that the output file is readable and the XML is valid.
When we run the same program in ECC 6.0. (after unicode check & changes done), the output xml file is generated and it is in unreadable form. (XML contains some machine characters). When we open the XML in Altova Spy, it shows the error XML is invalid. The erorr is 'character #x3F3C is grammatically unexpected'.
In 4.6c, they used the encoding <?xml version="1.0" encoding="ISO-8859-1" ?> . We changed the encoding to UTF-8 in ECC 6.0 since we are doing unicode conversion. (
<?xml version="1.0" encoding="UTF-8" ?> ). After this change also, the output file is not generated correctly. It is unreadable form. (Some Machine Characters).
Friends, What could be the problem ? . Can you help me to identify this problem.
Kind regards,
Jegathees P.

I troubleshooted that, the reason is that conversion of X to C (Hexadecimal to C) in the ASSIGN statement is not working correctly in ECC 6.0. Then, we replaced the code with our custom Function Module to convert xstring to string. After this, we got the XML correctly, readable and well-formed XML.

Trigger when generating/updating a PP resource(work center) in SAP ECC 6.0

Hello, SDN members.
The thing is: I want to mapp when a resource (transaction CRC1 ou CR01) is generated to trigger an interface other Non-SAP System.
I am used to use EXITs or BaDIs to mapp changes when it is about process orders, MRP, etc.
I have been looking around in SAP ECC 6.0 without success.
Does anyone could give me a clue of how can I mapp that? It applies also to updating a Resource (transaction CRC2 or CR02).

My question is that why step 4) doesn't work normally ?

No receiver could be determined while doing SAP ECC Integraion with MDM 7

Dear All,
Can you please help me to resolve the following issue.
We are doing SAP ECC Integration with MDM 7.1 by using MDM PI Adapter.
Source side we are processing MATMAS.MATMAS05 IDoc and Receiver side we are using MDM PI Adapter to Connect the MDM System.
I have checked the Configuration by using Test Configuration Wizard, it showing every thing fine there.
Is it because of any network connection issue at the Target system (MDM) side?
Plz check the error message for your reference;
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Mahesh

Hi,
From error looks like it is not failing at receiver determination step. if you all configurations are fine, then this could be because of system cache refresh.
Go to Edit mode in your scenario and again save it and activate it. Do a cache refresh and check if it works.
Regards,
Shiv

Working with badi in SAP ECC 6.0

Similar Messages

Maybe you are looking for