on 11-07-2008 9:23 AM
Hello,
Let me expose my problem.
In fact, I need to integrate new Goods Movements sent by a non-Sap system to ECC system.
To do that, the non-sap system sends a file.
Then, I need to generate from this file an Idoc (MBGMCR), fill this Idoc with some extra data (from Ecc tables) and then to integrate it into ECC.
The question here is to find the best solution (according to performance and feasibility) to do that using PI (7.0).
We are hesitating between two scenarios:
1- File to Abap Proxy
We get the data sent by an abap proxy, and then we complete it with the necessary extra data from ECC tables in order to create complete the Idoc segments.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Even, using PI will be a waste of performance/time (due to mappingu2026)
2- File to IDOC
This alternative looks more interesting (at least in the PI way).
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
For example, the file contains Orders headers and I need to generate Goods Movements for the materials contained in the orders. So I need to access Orders posts, to retrieve the materials data.
Is there a way to retrieve simple information in PI using ECC data?
Any other suggestion/comment is welcome.
(Any other scenario is also welcome)
Thanks you in advance.
-
Saber L.
SAP PI consultant.
Edited by: LMS LMS on Nov 7, 2008 10:24 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM
ABAP proxy would improve performance in terms of providing adapterless communication.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Making a direct connection would increase point to point connectivity across the organization whose reduction is one of the reason why XI is used.
If ur communication is async and u have the idoc structure ready, then u may proceed with Idocs.
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
If you want to prevent the node from getting generated, simply disable it in mapping.
I hope u have seen this
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ Prateek
First, thank you for the link. It is very interesting.
But, I can't really understand when you said
"If you want to prevent the node from getting generated, simply disable it in mapping."
In fact, file provides only header data; I need to fetch the post data from ECC tables.
@Sarvesh
Thanks you for your reply.
I am looking for a solution with combines both of PI monitoring & performance (SAP Retail environmentu2026)
Do you see an other way/scenario to do that in order to optimize this process?
But, I can't really understand when you said
In mapping, if u think that certain segments of the Idoc receiver structure won't be populated, just disable it.
I need to fetch the post data from ECC tables.
Could you elaborate this. U are saying u r doing the mapping of idoc header fields only using the source file. Then are you performing lookup of rest of the data?
Regards,
Prateek
Could you elaborate this. U are saying u r doing the mapping of idoc header fields only using the source file. Then are you performing lookup of rest of the data?
That is exactly what I need to do.
I maps the file data into idoc header (and some other segments).
The next step is to lookup for post data from ECC table in order to generate post segments of the idoc.
regards,
saber,
Still if some idoc segments are not required at receiver, then my comment about disabling that node holds true.
File to Idoc senario suits ur requirement well. You can compare it with abap proxy approach as per the advantages/ disadv mentioned earlier. Usually for async scenario with available idoc structure encourages Idoc usage. And this would also prevent Abap development at receiver.
Regards,
Prateek
HI,
SAP XI is middelware Component provided by SAP to seperate Design , Configuration , Monitoring of u r Integration
Hope this would answer u r first question.Chossing SAP XI to u r landscape is not meant not only for integration but also for futher place to view u r landscape interfaces and to enhance it.
The way u do wud block above functionality in futher wud be hetic find out the point of problem and enhancement wud b hard.
ABAP proxy wud giving out high performance when copamred to IDOC.But look out if u have abap resource for this
If u have IDOC std use it reduce u r coding and moreover empty nodes can be handled with the help of the mapping tat's not a problem
rgds
srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you can go for first option if you don't want any kind of monitoring via XI, but since you have XI as a middleware to monitor then you should use XI also but again it depends upon your choice..
In second option you need to have on RFC lookup function which will extract the neccessary data based on your requirement as given in below example by you.
> For example, the file contains Orders headers and I need to generate Goods Movements for the materials contained in the orders. So I need to access Orders posts, to retrieve the materials data.
In the second option since you have to use RFC lookup then there could be some performance issue.
So now it is your choice to chose which option is best for you.
Regards,
Sarvesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.