Hi Mahahir,
1) To address the issue with BAPI_ISUPROFILE_IMPORT, here are a few questions you will need to ask yourself:
- Are you passing the data in using the BAPI is one large call or are you breaking up the data into smaller packets? In previous implementations I have worked on, this is the typical way to ease performance issues by using parallelisation.
- How much data are you trying to load (i.e. 1 day of 15 minute data for 100 profiles = 9600 individual values)?
- What other jobs/programs are running at the same time? Are there semaphores applied to any processes when checking SM50?
- Have you checked the performance/configuration of the system with your BASIS team? Especially using ST02, DBACOCKPIT etc...
2) To address the issue with using AMI Enterprise Services:
- AMI web services are a change in technology, not a performance booster. Typically these are used when communication with an external system has the capability of communicating using web service calls directly from system to system using XML.
- AMI can offer customer enhancements up front when the data is received (i.e. extra validations) before EDM even touches the data. Its a nice touch when performing some validations up front.
- If your system does not have the appropriate resources (i.e. cores, RAM etc), then as Christian has stated, this is probably not a good idea to try this out.
Regards
Zane