Reg: PO interface from 4.7 to ECC 6.0

Hi Everyone,
I'm new to ALE/IDOC, Can anyone give the steps which needs to be followed to send POs thru IDOC from 4.7 to ECC 6.0.
Do I need to populate all the data like control segments, data segments or PO related details will be sent thru IDOC if we pass a particular details of that PO?
Pls give me some tips to proceed...

Hi,
You can use the IDOC Type: ORDER05 for this PO reqt. For PO the 850 EDI is used.
You need not fill in all the data for the segments, but only the mandatory fields & segments and along with some header details like Pur Org, vendor No, plant etc.
Based on some of the mandatory parameteres you fill in, it will be validated with the config already done in the SAP system.
Pls got to WEDI (Adminstrator Menu)- type it as a T-Code and you can go thru the details.
Apart from this the RFC destination needs to be set up in SM59 and the logical system settings in WE20 along with the port settings in WE21 has to be carried out.
Hope this helps.
thanka
JLN

Similar Messages

Interface from 4.7 version to ECC 6.0

Hi all,
We are having HR system in 4.7 version. We are implementing FI and Travel management in ECC 6.0 version. we need to have an interface from HR system to ECC 6.0 travel system. Which method is suitable for this?? Can we go for BAPIs??
Thanks in advance,
regards,
Chandra.

Hi,
If you want the data to be exchanged in a synchronus manner then BAPI's are the way to go.
However, as I see no need of the same there, ALE / IDOC's should be a preferred way of doing as you can configure the IDOC's to be triggered as soon as there is a change in the data.
And like you mentioned, both are SAP systems, so you wouldn't need a middleware, you can communicate using IDOCS'.
Regards,
Ravi
Note : Please mark all the helpful answers

Information on impact on interfaces due to upgrade from 4.7 to ECC 6.0

Hi friends,
We are upgrading from 4.7 to ECC 6.0. We have some interfaces with the SAP system in our current version.I need information on which of these interfaces will be affected due to Upgrade of the system to ECC 6.0
Mentioned below is the list
SAP R/3 --- CRM 5.0
SAP R/3 --- Xi PAY
SAP R/3 --- Vertex
SAP R/3 --- TEKRF
SAP R/3 --- Virsa
SAP R/3 --- WTX
SAP R/3 --- SOLMAN
It would be really helpful if you can just provide the initial impact analysis for these interfaces due to upgrade.Points will be rewarded.
Thank in advance.
Regards,
Pawan.

Hi
there are several oss-notes available which explain how to transfer your text customizing to the new procedure. This happens if you are uppgrading from a release 4.6c or lower. If you are already in 4.7, there should be no problem with text determination.
Regards
Rauno

Reg: Advantages from 4.6c to ECC 6 in terms of security

Hi,
Here I need inputs about the recommendations on different functionality or the advantages from 4.6c to ECC 6 in terms of Security.
So please give your inputs about the additional functionality and advantages
Thanks in advance.........
Regards,
Srini.

Hi Sirni,
A lot of difference from 4.6 to ECC6 with future wise and security wise.
You can see the complete details in help.sap.com
Rgards,
Anil

Error while RRI from BW reports to ECC CJI3 transaction

Hi All,
When we try to set up RRI from BW reports to ECC CJI3 transaction, we get an error message (Stop message):
You cannot use the report-report interface to call up report RKREP000
Diagnosis
Line Item report RKPEP000 is not suitable for the report/report interface
Procedure
Always enter RKPEP000 as the receiver report for project line items in the report/report interface. This program uses the transfer parameters to determine which line item reports can be accessed.
<b>As per the other reply tried the ABAP Report RKPEP000/3 also ..no use ..
can you please suggest , how to go about this CJI3 issue for RRI , what settings need to be done in the RSBBS ...</b>
We have attemped to use "S_ALR_87013543" as well but the parameters don't go through properly which means when a user jumps from a BW report, they end up at the ECC selection screen of S_ALR_87013543.
Drill through is working for our Cost Center reports. Just not this one in particular.
Any advice would be greatly appreciated.
prasad

Hi,
I'm facing the same problem so please If you have found some solution please tell me what should I do to use RRI from BEX query to CJI3 transaction.
Regards,
Ana

What are the key points to beconsider while upgrading from 4.7 to ECC 6.0

hai
What are the key points to beconsider while upgrading from 4.7 to ECC 6.0
please provide sufficient material
points will be rewarded
regards
v.sridhar

Hi Sridhar,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, and QM.....
Click on Search
then it displays the Release Version and the Delta Functionality. Which can be downloaded to a word document if required.
And also check the release notes of ECC 6.0 in service.sap.com.
When you are upgrading from 4.6C to ECC6
Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).
To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).
Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't require solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Major difference is ECC6 is netwear product having WASJAVA+ABAP
secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.
Please go through the link that is shown here and if there is any doubts then feel free to ask.
Major difference is ECC6 is net weaver product having WASJAVA+ABAP
secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't required solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Please also Refer sdn thread and make a small search where u can find lot of information Reg this
olution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Refer below and search for posts on this topic on sdn
There are so many differences between the version in different objects
I
These are the some of the settings that are differed in the two versions and in that two objects
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
Upgrade from 4.6c to 6.0 ECC
upgrade from 4.7 to ecc 6.0
Please Do Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

How to copy/send text file from FTPS to SAP ECC File Port

Hi Frdns,
I am working on one design, actually my requirement as follows
I am receiving financial information document from Banks, which is in the form of BIA2 message format, it looks like text file. This information needs to be sending to SAP ECC system.
I identified some approaches to full fill the requirement
1)Using Conversion agent/or third party tools to convert BIA2 message in to XML, then using PI I will pick up the XML message, convert it in to IDoc.
2)Without any conversion I will copy the same file (original BIA2 message) in to SAP ECC file port, in this case no conversion required, calling some program I will schedule it.
I am looking forward t implement the second approach because it saves lot of money to my client.
Now I am wondering using File adapter can i copy to SAP ECC File Port or I required ABAP proxy?
What is the best approach to copy the BIA message text file from FTPS to SAP ECC File Port.??
Regards,
Raj

Hi Raja,
>>Now I am wondering using File adapter can i copy to SAP ECC File Port or I required ABAP proxy?
Yes you can do this copy, the only restriction that can happen is the file size.. If you are sure that the fiel will be of few MB at the max then you can use the Configuration part alone and copy it to ECC folder. For doing this you need the following:
1. Sender agreement (mention the sender interface as anything XYZ)
2. Sender communication channel. Pick the file in binary mode
3. Receiver determination (keep both the sender and receiver service as same)
4. Interface Detemiantion (dont specify any mapping and keep the receiver interface name as XYZ)
5. Create receiver agreement (with same service and interface)
6. Use file adapter here
Regards
Suraj

Table Enhancement Category during upgrade from 4.7 to ECC 6.0

When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables. The enhancement category was previously u2018not classifiedu2019 on these tables.
Is this really necessary? Has anyone not changed the enhancement categories on tables that were flagged during the upgrade? Also, what happens if we select the wrong enhancement category?

Jane,
This is what SAP says,
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

Steps to follow in Upgrade from 4.7 to ECC 6.0

Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
Reddy

Dear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues

Problem in transmitting the RFx Award from E-Sourcing to ECC

Hello,
We have integrated the E-Sourcing and ECC environment, when we are transmitting the RFx from E-Sourcing to ECC through SAP PI7.10, we are getting following HTTP 403 error:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=abc123&sap-password=abces&sap-client=001&sap-language=EN. Please contact your system administrator.
I believe that the error are for common cause and possibly the Integration engine is not accepting HTTP request. We have assigned almost all security profiles to the user in the SAP PI Box, as basic assumption is that it looks like these error due to security reason.Kindly help.
Also we are not using HTTPs services, is it mandatory as we are using only HTTP protocol.
Thanks and Regards,
Satish

Hi Shri,
1. We are upgrading from E-Sourcing 4.4 to 5.1 and changing the database from Oracle to db2. Would this have any effect on the reports? would the reports have to be re written again?
Ans: Yes you will need to modify the reports according to DB2. or raise it to SAP if they have some standard tool for same
2. The upgrade is mainly to use the portugese language support in 5.1 SP02. Also would you suggest SP02 or any other Service Packs after SP02?
Ans: I will suggest to go with SP06 as SP05 has lots many bugs
3. Does SP05 have portugese language support? In the documentation i have not seen anything about the portugese language support for sp05.
Ans: Must be supporting as it is higher version.
4. Also we plan to integrate e-sourcing to ECC or SRM. what are the pros and cons if we integrate it to SRM Vs ECC? what do you recommend?
Ans: Check above post
~Ankush Mittal

Creating shopping cart in SRM through an interface from an external system

Hello,
i am currenlty working on a SRM implementation at a client and we are looking into
building an interface for purchase requisitions from an external system to SAP.
To be able to get these requisitions as a package approved I would want them to go though the
approval process in SRM. Does anybody know if it is possible to create a shopping cart in SRM through an interface from another system?
thanks,
Geert

SRM has a standard business scenario of PDP PM
here the external requirements are transferred to SRM for sourcing
in normal business scenario ECC PR is transferred to SRM which creates a dummy SC or say sourcing SC in SRM which appears in Purchaser's worklist after correct settings
SRM can work with NON SAP system also
so logically yr requirement should be possible
but in ECC PR transfer case the SC created in SRM is already apparoved.
BR
Dinesh

Error while deploying a PAR file from NWDS into an ECC.

Hi all,
I am getting this error while deploying a PAR file from NWDS into an ECC.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
My server is running properly
1 - Where is sap-plugin.log file? I don´t find it.
2 - Could there be another file with another name with information about the error?
3 - Is there another way to deploy the file directly from the ECC?
Regards,

Hi,
Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
Windows/ Prefereces / SAP Enterprise Portal
Check the following enteries
Alias
Host
Port
Login etc.
Regards,

Data Migration from Legacy system to ECC systems via ETL through SAP PI

Hi All,
I wanted to know if we can migrate the data from Legacy systems to ECC systems via PI.
What I understand is there is ETL tool is used to extract the data from legacy system, and what client is looking to load that data via PI?
Can we do that ? I am concerned because this will involve mass data?
If I have to use PI , I see option of PROXY / IDOC /FILE as receiver in ECC system (take the data from ETL)?
Can somebody has done this earlier , please share the approach.
Thanks,
Pushkar Patel

Hi ,
I require few details from you.
1. What ETL tool you are using, If Informatica, it already have PowerConnect to connect to SAP. So you can create source and Target Structure and also you can use RFC's to send data to R/3. Else, for other ETL tools, can you prepare RFC's or any other way to send data to R/3. let me know the tool.
2. Does R/3 contains the master data tables? If yes, then try to use LSMW for Mass upload of data to tables.
If your client don't want to use either of these options please elaborate, what is the case.
Regards
Aashish Sinha

Interview questions on upgrades from 4.7 to ECC

Hi,
Can any one please post some potential areas/questions that will be asked for upgrade projects from 4.7 to ECC6.0
Points will be awarded.
Thanks

Hi Frank,
this is good question, why because sap upgrades from 4.6b to ecc 6.0 is very risky.
take one example , in 4.5b , me21n application having 620 screen where as in ecc 6.0 having 9000 screen . that time we will take care of it.
check the obsolete function modules , 4.5b , having ws_upload, ws_download.... use cl_gui_frontend_services , under these having differnt type of methods.
once you change the code in ecc , go to tranx : SLIN check the error where it is exact.

Using local session bean interface from web container using EJB 3.0

Hi,
How can you use a local session bean interface from Java (rather than data controls) in a web container using EJB 3.0?
I can use a remote interface by looking up InitialContext, but I can't find a local interface this way (even from another session EJB). I can use a local interface from an EJB using annotation "EJB", but as I understand, this is not available in the web container.
If I try to add an ejb-jar.xml file, these seems to mess up by project...
Hope you can help.
Roger

The portable way to retrieve an EJB reference in Java EE is to either inject it or look it up via the
component's private naming environment. The simplest way is :
@EJB
private DocumentManager dm;
The global JNDI name is only used as an implementation specific way to uniquely assign an
identifier to a specific Remote EJB. It's best for this not to appear directly in the source code.
There's more on global JNDI names in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
The alternative to annotations is to use an ejb-ref to declare the ejb dependency. The ejb-ref
is declared in the standard deployment descriptor corresponding to the component doing the
lookup. Each ejb-ref has an ejb-ref-name, e.g. <ejb-ref-name>DM_ref</ejb-ref-name>
The code looks up the ejb-ref-name relative to the java:comp/env namespace to retrieve the
EJB reference.
DocumentManager dm = (DocumentManager)
new InitialContext().lookup("java:comp/env/DM_ref");

Reg: PO interface from 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for