Sending IDOC-xml to R/3 system

Hi all
I am doing a bypass File to Idoc scenario.we taking the input file as idoc xml and sending it to R/3 system for IDOC generation.Every thing is normal but in SXMB_MONI its showing Obligatory node E1EDP10 missing while that segment was persent in the input file then we just replaced <E1EDP10> by <E1EDP10 SEGMENT="EIEDP10"> elated! it worked I thought the problem was solved "EUREKA"........But now the client is telling we should not hardcode any value in the input file they have provided i.e we shouldn't add the segment attribute.
Its bypass thats why we can't do mapping also......now we r puzzled ........
can we achieve this by changing the XSD of idoc converting the segment attribute required to optional? or what should be do plz tell us as its urgent.........
Regards
saurabh sharma

Pls avoid creating new threads for the same problem when you have a thread already open for the same issue.
Regards,
Jai Shankar

Similar Messages

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

Need of XI to send an XML from one SAP system to another SAP system

Dear colleagues,
I work in the SRM solution.
In SRM there is a Purchaser and Supplier scenario called Supplier Self Services.
The Purchaser creates a Purchase order and sends it to the supplier in form of an XML file.
The purchaser system and supplier system are the same SAP system but different clients.
Example: Purchaser client is 300 and Supplier client is 330 and both of them are on the same system.
I have a very basic question.
Currently we have the XI system which acts as an interface to send the Purchaser PO XML to the Supplier as XML.
a)My question is in case the XML structure is identical across both the clients, then what is the need of XI system?
b) Is it not possible to send XML from one client to another without an XI system? there si no need of any message mapping required since I am expecting the same XML structure in both clients.
Please clarify the need of XI system in the following scenario. Is it not possible without XI?
Many thanks.
Best regards,
Srivatsa

Hi Srivatsa,
YOu can send the XML message from one sap system to another sap system even without an XI system in between.
But the use of SAP XI (Or any other middleware) is recommended because, it gives you the following advantages.
1) Better monitoring and alerting mechanism. XI provides you robust set of tools that let you monitor the status of the messages that are exchanged.
2) Direct communication between systems is referred to as Point to Point communication, which has its own disadvantages as against Hub and SPoke model (Message exchange using XI).
3) Message delivery is guaranteed if you have XI in between.
If the target system is down, the sender sap system will not try multiple times to post the message.
But if you use XI, it can be configured to send the message multiple times, till it succeeds.
Regards,
Ravi Kanth Talagana

How to send IDOC XML to ftp or other servers using ABAP

Hi,,,,,,EXPERTS
I m able to generate IDocs in XML format,
using the XML port definition in SAP. The XML file is generated in the application server, in the physical directory specified in the port definition.
The application server in on Windows operating system.
Now i need the files to be generated on another machine whose ip address and location is known, insted of being generated on the application server.
Pls can anyone help me in this.
waiting with lots of hope...dear frnd pls give me a step by step process to get this...
thx,
ram.

Hi Mahesh,
Thanks for your reply.
My requirement is bit different. i have to send Open PR data for diffrent materials. In a 3rd party application user will search for few materials which will generate a report that will show the PR related data for those material.
That means for few selected materials there will be few PR's which may be open, i have to show those in my report.
Eg: material A, B. are in PR 00001 & material B, C in PR 00002.
After selecting materials A to C report will show
Material                 PR No                   Item No                Quantity
A                           00001                    10                             1
B                           00001                     20                            3
B                           00002                     10                            3
C                           00002                      10                           1
Same thing i have to do for open PO & open Sales order also.
Can u please help me to provide the solution how can i proceed for it. U have given the Message type & a bapi how it will help in my issue?
I got a suggesion from someone that extend message type matmas for PR, PO, SD related data & send the idoc. but i am confused how to pass that much data ina single IDOC.
Regards,
Nik

Send Idoc's to R/3 System with logon group

Hello everybody,
I have the next scenario
Sender R/3 Idoc -> XI -> Receiver R/3 Idoc
now I have a doubt, the receiver system has a logon group, is there any benefits for me in XI to use the logon group to send the Idocs to this system?, and if it's better to use logon group how can I use it, juts by defining the RFC that exists in SM59 that points to the receiver R/3 system in XI as load balancing and pointing to the logon group????, thanks in advance for your answers.

Julio,
Yes you are right, load balancing can be achieved using logon groups in the RFC destination for the IDoc adapter. It basically enables the ABAP dispatcher to decide whats the best available application server to process the inbound message sent by PI.The purpose is to load-balance successive connections across a group of ECC application servers.
To do this a connection is established through the message server (the central ECC instances communication process) to determine which ECC instance is to handle the RFC call.
The key parameters here are:
u2022     the hostname, on which the message server process runs,
u2022     the system name of the ECC central instance, and
u2022     The logon group, which indicates the cluster of applications servers that an ECC instance will be selected from, to serve the request.
Greetings,
Gerardo.

Addition data send in XML po to external system In SRM 7

Hi Expert
How we can add/ Modify data for XML PO Which sending for external system Via PI .
we need to add additional data to the XI system in XML format in PO . How we can add the code to this.
One more issue is like we are not able to debug the BADI BBP_SAPXML1_OUT_BADI.
Request to reply for this

Hello sharad,
Please find the sample coding.
METHOD if_ex_bbp_sapxml1_out_badi~purchaseorder.
DATA: l_str(40) TYPE c,
        ls_partner TYPE bbps_pdext_partner,
        ls_item TYPE bbps_pdext_po_item_d,
        ls_proxyitem TYPE bbpx1_purchase_order_item,
        ls_partner_item TYPE bbpx1_po_ship_to_location,
        ls_fdspartner TYPE bbpx1_po_ship_to_location,
        ls_telephone TYPE bbpx1_address_telephone,
        ls_check TYPE BBPX1_ADDRESS,
        ls_fax TYPE bbpx1_address_facsimile,
        ls_email TYPE bbpx1_address_email,
        l_index TYPE i,
       lt_table TYPE TABLE OF ztest_db,
       ls_table TYPE ztest_db,
        l_flag TYPE c,
        ls_dfkkbptaxnum TYPE dfkkbptaxnum,
        lt_telephone     TYPE bbpx1_address_telephone_tab,
         lt_check                TYPE BBPX1_ADDRESS,
        lt_email       TYPE bbpx1_address_email_tab,
        lt_name        TYPE bbpx1_person_name,
        ls_name         TYPE bbpx1_person_name,
        lt_street       TYPE bbpx1_address_physical_address,
        ls_street       TYPE bbpx1_purchase_order_party,
        ls_details        TYPE bbpx1_purchase_order_item,
        lt_ship        TYPE BBPX1_PO_SHIP_TO_LOCATION,
        ls_ship        TYPE bbpx1_po_ship_to_location.
LOOP AT cs_purchase_order_message-purchase_order-item INTO ls_proxyitem.
    l_index = l_index + 1.
    LOOP AT it_item INTO ls_item WHERE number_int = ls_proxyitem-id-value.
      LOOP AT it_partner INTO ls_partner WHERE p_guid = ls_item-guid.
        IF ls_partner-partner_fct = '00000712'.
          ls_proxyitem-zzxyz = ls_partner-zzxyz.
         ls_proxyitem-zzxyz = 'Test'.
          ls_fdspartner-buyer_id = ls_partner-partner_id.
         concatenate ls_partner-NAME ls_partner-NAME_2 into l_str separated by space.
          APPEND ls_partner-name TO ls_fdspartner-address-organisation_formatted_name.
          APPEND ls_partner-name_2 TO ls_fdspartner-address-organisation_formatted_name.
         ls_fdspartner-ADDRESS-ORGANISATION_FORMATTED_NAME = l_str.
          ls_fdspartner-address-physical_address-country_code = ls_partner-country.
          ls_fdspartner-address-physical_address-region_code-list_id = ls_partner-region.
          ls_fdspartner-address-physical_address-street_postal_code = ls_partner-postl_cod1.
          ls_fdspartner-address-physical_address-city_name = ls_partner-city.
          ls_fdspartner-address-physical_address-street_name = ls_partner-street.
          ls_fdspartner-address-physical_address-care_of_name = ls_partner-c_o_name.
          ls_fdspartner-address-physical_address-district_name = ls_partner-district.
*-- Populate telephone number
          ls_telephone-number-subscriber_id = ls_partner-tel1_numbr.
          ls_telephone-number_default_indicator = 'true'.
          ls_telephone-number_usage_denial_indicator = 'false'.
          APPEND ls_telephone TO ls_fdspartner-address-communication-telephone.
*-- Get Fax details
          ls_fax-number-subscriber_id = ls_partner-fax_number.
          ls_fax-number_default_indicator = 'true'.
          ls_fax-number_usage_denial_indicator = 'false'.
          APPEND ls_fax TO ls_fdspartner-address-communication-facsimile.
*-- Get Email details
          ls_email-address-value = ls_partner-e_mail.
          ls_email-address_default_indicator = 'true'.
          ls_email-address_usage_denial_indicator = 'false'.
          APPEND ls_email TO ls_fdspartner-address-communication-email.
          ls_proxyitem-zfinal_destination = ls_fdspartner.
          MODIFY cs_purchase_order_message-purchase_order-item INDEX l_index FROM ls_proxyitem.
          CLEAR ls_fdspartner.
        ENDIF.
        IF ls_partner-partner_fct = '00000027'.
          ls_proxyitem-zzcxyz = ls_partner-zzcxyz.
          MODIFY cs_purchase_order_message-purchase_order-item INDEX l_index FROM ls_proxyitem.
          l_flag = 'X'.
        ENDIF.
      ENDLOOP.
      IF l_flag IS INITIAL.
        READ TABLE it_partner INTO ls_partner WITH KEY partner_fct = '00000027'.
        IF sy-subrc = 0.
          ls_proxyitem-zzclxyz = ls_partner-zzclxyz. " custom field
          MODIFY cs_purchase_order_message-purchase_order-item INDEX l_index FROM ls_proxyitem.
        ENDIF.
      ENDIF.
    ENDLOOP.
ENDLOOP.
ENDMETHOD.
Edited by: S Neelima on Apr 14, 2011 11:17 AM

Sending Idoc xml into websphere MQ using a ABAP

Hello Experts,
I have requirment where in I need to send a IDoc in zml format in to Websphere MQ. Is there any chance of doing it? If so how can I achive it?
Thanks,
'Sandhya

hi,
you can check these function modules to convert idoc data to xml format.
ISIA_CE_IDOC_TO_XML.
CFG_API_CONVERT_IDOC_TO_XML
IDOCS_OUTPUT_IN_XML_FORMAT.

Issue with Chinese characters while sending IDOCs from PI to SAP system

Hi,
We are working on File to IDOC scenario where in some of the fields are having Chinese characters. In SAP system, we noticed that the Chinese characters are getting replaced with # where as in PI output payload we are able to see the correct Chinese characters. The systems involved are PI 7.4 and SAP ECC -6.0.

Like in dual stack where we have an option to choose unicode/ non-unicode, i don't see any option in single stack.
However not sure if it works but you can give a try..
I assume you have created the RFC destination in NWA.
Go to RFC destination ->Specific Data -> Advanced Settings - here we have an option to mention the code page.
You might want to mention the code page for chinese char and see if it helps..
Before doing this, do checkMark's suggestion.

ALE: Sending IDOC inbound from non-SAP system

Hi
How does one need to setup the SAP system to accept data from an external non-SAP system. Should one setup some sort of conection to trigger an import to SAP?

Hi,
On the SAP side you need to create a partner profile in T.code: WE20 of type LS. And add the message type, idoc type in the inbound parameters section of it.
And you must also specify the partner number you created here, on the IDoc control record.
This link from SAP help, will provide some addition data.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm</a>
Hope this helps.
Regards,
Sumant.

Howto Send IDOC to third-party system. programID can not be registered.

Hi, guys.
I want to post IDOC to a third-party system through XI. And for sure, the third-party system can receive IDOC.
In the receiver communication channel, I would fill in the RFC Destination with a RFC connection defined in SM59.
In SM59, it is a tcp/ip connection and in technical settings the activation type is Registered Server Program. I name the Program ID randomly with 'a.a'. In Gateway Options, I fill the host with XI server and service with sapgw01.
Then I test the connection, the result is program a.a not registered on XI server.
My question is how to register the progam when I want to use this RFC to send IDOC to the third-party system. And how the RFC know which system he would connect. I don't find anyplace with the connection information such as IP or something like this.

Sergio Cipolla
Thank you for your material. I have read the doc you refered.
Almost I understand the process, there is one part.
I should register the program ID in saprfc.ini file with the following content:
DEST=FROMXI
TYPE=R
GWHOST=saphost
GWSERV=sapgateway
PROGID=a.a
Here I am wondering the fiield "DEST" represent for. Does it mean the hostname of the target external system?
And Here is the UNIX system, what is the path location of the file saprfc.ini or where I should put this file to be effective.
Thanks in advance.
Bu Ju

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

Problem while sending IDOC to File Senario

Hi Experts
    I am having problem while sending the Idoc from SAP R/3 to File
   I have done all the setting in SAP as well in XI but while pushing IDOC
   I am getting error in the transaction sm58 in SAP R/3
" <b>The service for the client 300(My SAP R/3 client) is not present in Integration
Directory</b>"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Idoc xml message in JMS adapter

Hi All,
Question 1:
My scenario is MQ series(JMS adaptr) to SAP(IDOC adptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series will send IDOC xml. In such case shall i need to do content conversion at JMS adapter level or not.whthr IDOC xml can be directly handle at Mapping level without doing any content conversion in adapter level.
Question 2(viceversa):
SAP(IDOC adptr) to MQ series(JMS adaptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series expect me IDOC xml. How to handle content conversion at JMS recvr adapter level.
my assumption only in case of (xml to plain) and (plain to xml) require content conversion here my Input and output is IDOC xml.

Saravanan,
As Expert Vishnu Mentioned,
>In such case shall i need to do content conversion
NO need to use
>How to handle content conversion at JMS recvr adapter level
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-adapters/how%20to%20use%20the%20content%20conversion%20module%20with%20xi%203.0%20j2ee%20jms%20adapter.pdf
Cheers
Agasthuri Doss

IS SENDER IDOC ADAPTER NECESSARY?

Hi,
I read somewhere that to send IDOC from one R/3 system,we need not to create any sender IDOC communication channel,bcoz while creating it we dont specify any technical details.
Is it true?
Why dont we need any sender IDOC channel?

Hi,
no you don't NEED it
but it's a good practise to create it
with a sender agreement
(if your SP allows that)
as in the future there might be some
additional features which you will be able to use
with that
BTW
use the directory wizard to find out
if it will be created by defaut or not
Regards,
michal

Sending IDOC-xml to R/3 system

Similar Messages

Maybe you are looking for