on 09-06-2006 10:21 PM
Hi,
What kind of complications we may face (or you people faced )while using Adapters like
1.File
2.IDOC
3.RFC
Thanks
Seshu
Hi,
Just to add some more
1) File
- File Content Conversion problems for multiple structures in the sender side
- Reciever side , problem with content comversion for fixed field lengths
-Operating system command execution
2) Idoc
- Improper configuration of Partner profiles,Port Maintenance, Logical system problems, metdata refresh etc
- If you change the metadata in the R/3 system, then re-import the strcuture into XI and refresh the cache and also with IDX2 transaction
3) RFC
- Metadata Refresh is the problem. Many a times, you will end up with restarting the RFC adapter in the J2EE engine.
- Another runtime error may be Application Error .. this may be because of non-availability of the resource because of huge messages, data type mismatch problems or huge number of messages
- it is prefer not to use Dialog user id for the RFC/Idoc adapter configuration .. it will throw error after the expiry.
-If Program Id is not redgistered i.e in the R.3 RFC destination of type TCP/IP should be cofigured correctly..
Hope this helps,
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Seshu,
A suggestion.. Take a look at Michal's XI FAQ blog here..
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
You would get an idea of some of the basic problems which you are likely to face.
cheers,
Prashanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Seshu,
This is a pretty generalised question
Problems I had faced when I started off..
File adapter :
Content Conversion parameters usage
UTF encoding
IDOC adapter:
Unable to convert sender service to an ALE logical system
(as far as I faced )
RFC adapter:
RFC_Application error
RFC timeouts( due to heavy message payload)
cheers,
Prashanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
>>>>1.File
difficulties to handle many structures
- structures with lines + sublines
- with trailers and other file input which is not necessary in the messages
hard to manage big files...
>>>>2.IDOC
no issues
>>>>3.RFC
diffculties to handle big messages (many mb)
gateway errors with first XI SPs
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There is not especially complication for these 3 adapters, coz they are the most popular! and there are many documents/weblogs.
1.File => Easy
2.IDOC => Need an ALE configuration, thus it's a little more complex. And mapping will be perhaps complex, coz notion of "context" across IDoc segments: it depends of your IDoc and of your functional rules.
3.RFC => Normally with a RFC, we work in <u>Synch</u>ronous mode. For instance with a RFC like "xxx_GetDetail_Customer".
Mickael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.