 Forum main
page
Most
active member
Login page
Register
Log out
Search page
View our event calendar
Add general event such as an upcoming
software release or conference
View all birthdays
Public image gallery
Upload your images in your profile
Profile editing page
Subscription list page
Address book page
Member list page
View the
most active member
User groups listing
Private message page
|
SAP RFC Interface stucture problem with Adapter for SAP Proxy transport
View related threads:
(in this forum
| in all forums)
|
Logged in as: Guest
|
|
Users viewing this topic: none
|
|
Login  | |
|
SAP RFC Interface stucture problem with Adapter for SAP... - 4 May 2005
|
|
|
ruud
Posts: 5
Score: 0
Joined: 19 April 2005
Status: offline
|
Dear Mr, Mrs,
We are using the evaluation version of BizTalk Utilities Adaptor for SAP 2004 in combination with SAP .NET connector 1.0.3.
When trying to sent data to SAP we encountered the following problem when mapping the import_xml to the generated Request schema*:
(see attachment for screenshot's of the non working version).
If the interface parameters (Import or Tables) in SAP are based on Reference structures no data is transferred to SAP (allthough the RFC is correctly called since the ‘expected’ SAP returnmessages are generated, eg. ‘Header contains no data’).
When we define the RFC Importparameters in SAP directly referring to SAP datafields the import-data is correctly transferred to SAP .
The latter is however no solution since allmost all RFC’s/BAPI’s contain Importparameters based on reference-structures and indeed the Tables interface is allways based on reference structures.
We also tried the demo version based on BAPI_BANK_CREATE (which I modified to put a ‘commit’ command in the SAP source).
In this case the Import fields Bankkey and Bankcountry (which are referred in SAP to datafields BAPI1011_KEY-BANK_KEY and BAPI1011_KEY-BANK_CTRY) are transferred to SAP correctly but eg. Bank_Name which is part of parameter Bank_Addres with reference stucture BAPI1011_ADDRESS is not transferred.
*) If we connect directly to the SAP .NET connector in VB .NET using the same import-xml everything is working fine.
Are we doing something wrong, wrong version? or is the described behavior indeed a problem?
For your info, we are on SAP release 46C support package level 47.
Kind regards,
Ruud van Rijn
 Attachment (1)
|
|
|
|
|
[Deleted] - 1 March 2006
|
|
|
Deleted User
|
[Deleted by Admins]
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version
Email TopXML