Sending IDOC's to many partners

Hello all...
the problem i am facing is that for example I have 100 partners and i have to distribute material master data to all 100 partners. If so do i need to execute BD10 transaction for 100 logical system's seperately ,because the logical system is mandatory there.Else is there any other way to send the data to 100 partners at a time.
I have heard about the parallel processing in BD10. that we have to group the partner 's ....if so how can that be done .....could you all help me out in this doubt..
thanking everyone in advance
chandu reddy

Hi,
By using BD10 you can send for one system only.Parallel processing is different means if you have 500 idocs for one system then all these 500 idocs will be split among different work processers.In your case parallel process is not the solution.For your requirement you have to write small custom program with loop of all partners,with in loop you can use SUBMIT BD10.This one way of solution.
Thanks,
shyla

Similar Messages

Idoc to Different Trading partners using AS2 Adapter

Hello experts,
I have a requirement where we have to send an Idoc to different trading partners using van.
On the receiver side AS2 adapters will be used.There are many trading partners here.Can someone guide me through? ..
The entire scenario will be done in SAP PO 7.4
Breaking the entire scenario in the following parts---
1)IDoc on sender side--What will be partner profile type? Will it LS or any other (BP, GP or KU??)
2)AS2 configuration details---AS2 adapter is available in the dropdown of adapter list.What are the config details for AS2?
3)Trading partner mechanism-How this can be achieved?..what this essentially achieves ? any step by step guide available? Does it take care of sending the Idoc only to VAN or sending Idoc to different trading partners directly bypassing VAN?
4)Is using NWDS suggestible?--Is it convenient?
Any help/step by step blog will be of great help.
If I miss anything in the entire scenario, please let me know
Thanks
Ayan Chaudhuri

Hi Ajay,
1)IDoc on sender side--What will be partner profile type? Will it LS or any other (BP, GP or KU??)
-->>The partner type is depend on your scenario. AS2 adapter is used for B2B communication and usually to vendor and customers.
This purchase Order should go to the particular vendor as a sales order. Then we use partner type as LI -- Vendor.
Similarly when we sell some materials to our customers, we create the Sales order to our customer. Then we use Partner type as KU - Customer
Partner Type GP---Business Partner
Partner Type KU---Customer
Partner Type LI---Vendor
Partner Type LS---Logical system
Partner Type US--User
2)AS2 configuration details---AS2 adapter is available in the dropdown of adapter list.What are the config details for AS2?
-->> to configure as2 connection you need following details from trading partner
AS2 ID
server address with URL extension
TP certificate
MDN address and type (Sync, asyn and signed or not signed)
Message communication encryption algorithm
Compression is required or not and if req. which algorithm to use
3)Trading partner mechanism-How this can be achieved?..what this essentially achieves ? any step by step guide available? Does it take care of sending the Idoc only to VAN or sending Idoc to different trading partners directly bypassing VAN?
-->> If you are communicating through VAN then you need to send the message to VAN and VAN will route the message to respective TP.
4)Is using NWDS suggestible?--Is it convenient?
-->> NWDS is another option to create scenario, it is depend on developer which one he want to use.
The belog blog might be useful
Easy-to-use AS2 software - part IV
B2B- EDI Inbound -Step by Step Configuration
regards,
Harish

Steps required for Sender IDOC adapter PI 7.0

Hi all,
My basis guy has installed SAP EHP1 for PI7.0 for handling the idoc packaging(sending idocs in packs)...
Please can any one let me know the further settings required in PI after it has been installed...
and even when i open the sender IDOC in comminication channel in ID i am able to see only 3 options
Transport prtocol, message protocol,Adapter engine...
But i am not able to see the other fields...
Can any one help me...
Thanks and Regards,
sridhar

Hi Michael,
Thanks for your reply..
I searched for the docs in many ways.. but couldnt find proper information regarding the IDOC packaging with sender IDOC adapter and steps required...
Could you please let me know if i can get the book in Singapore since our project, because almost 90% interfaces are related to IDOC...
And request you if you can share me the steps required in PI to confirgure IDOC packaging for EHP1...
Regards,
Sridhar Reddy
Edited by: sridhar reddy kondam on Jun 15, 2009 4:35 AM

Send IDoc to Multiple Ports

Hi,
I have a custom IDoc message type YYY17101[Custom Type]. I need to send IDoc using this message type to 2 different rfc destination. The two RFC are
1. SAP R/3 system
2. XI system
My question is which partner profile type i have select to send IDoc using message type YYY17101.
Can i use partner profile type LS for sending IDoc to SAP R/3 and Partner pofile type US for XI system?
Thanks
aRs

Hi aRs,
Your challenge is in fact not so very difficult.
First you define both R/3 and XI as an LS-type partner in your system, since both systems need to receive a message from your target system.
Then you must use transaction BD64 to create a modelview (or choose in SALE the path Modelling and Implementing Business Processes --> Maintain Distribution Model and Distribute Views).
Create your own NEW model.
Use Add message type to add your specific message and supply your own LS system as source and the first target LS system (R/3).
Use again Add message type to add again your specific message and supply your own LS system as source and the second target LS system (XI).
If you view your model you will see ONE source system (your own) and TWO target systems (each with the same message below it).
You can add filters to the message (to prevent incorrect messages to be send) if these are defined in your own IDoc.
Now you can distribute this model to the target systems (in the menu choose: Edit --> Modelview --> Distribute.
If the partners in question can be reached this goes OK.
If all went well, go to the target systems and start transaction BD64 and select the model there. Then choose from the menu: Environment --> Generate partner profiles.
At this point your ALE customization is complete and communication has been setup.
So as you see, it is possible.
Regards,
Rob.

Send idoc to other system via SOAP

Hi,
I intend to implement an interface with other system non SAP, to send idocs via SOAP.
I've read some documentation on sdn but i'm very confused about Was / XI / BSP and some others terms.
Please, can someone help me, driving me to the right way and where to start ?
I don't know either if this the best solution to send many idocs... I'm talking about 10000 idocs each time.
In advance, thanks.

Vitor,
I suppose u want to distribute data of Idocs to a system which accepts SOAP request. For the same u can use XI with necessary distribution model on R/3 side to post the IDoc to XI and XI SOAP receiver adapter making a call to necessary SOAP server to post the data.
Regards
Rajeev

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
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
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.....

Send IDOC Messages In Order to XI

Hi,
I am using Job Scheduling for sending the list of Vendors(CREMAS IDOCs) to SAP XI from SAP R/3.
I am generating a unique ID for each vendor received. Just because all the messages reach XI at the same time, I am getting the same ID for many Vendors.
I am using Mapping Look up to get the maximum ID. I am then adding one to the maximum number and generating the new ID.
Is there any way to solve this problem?
I would like to know if I can process the messages one after the other to solve this issue.
Regards,
Venkatesh

hi,
2 ways:
1. send IDOCs in queue (possible only is your ERP is on WAS 6.40 or more)
2. use table IDXQUEUE to queue them inside XI
both approaches described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Sending IDoc from R/3 to XI -ongoing

Hi,
With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any one advise me on this?
Thanks & Regards
Manish

Hi,
There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
Under one tree I have tested the XML message and found the below error:
Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
Regards,
Manish

Sending IDOC from XI to R/3

Hi All,
I have created an IDOC - XI side here i am sending IDOC XI to R/3 it is showing Red Flag in SXMB_MONI but it is not showing any errors what will happend...? can any body suggest me the solution..?
Thanks
Sudheer

I hope you followed these steps for posting the idoc out of r/3.....
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed

Sending IDocs from ForEach Block from BPM disables my XI for 10 Minutes!

Hi guys,
I have a scenarion, where my SOAP adapter sends XML into XI, this passes it into BPM, which splits this XML in block to multiple IDoc and these are sent into R/3 system. This really works, but unfortunately, when I send the message into the SOAP adapter, my BOX is unavailable for cca 10 minutes and the documents contains only 2 IDocs!! After these 10 minutes is everything ok and the IDocs are in the R/3 system ...
What could be wrong??
Any idea is welcome, thanx in advance!
Peter

Michal,
First I tried to do this with my BPM:
before the change, I was mapping the message to IDoc directly in the BPM block part (I had abstract interfaces for message and for IDoc) and sending the Idoc away from the BPM
after the change, I tried to send away from the BPM just the message and try to make mapping to IDoc on the way from the BPM to rhe R/3 system
(it didn't help, my box was unavailable for 6minutes again)
I checked the BPM - sending of the both massage was in the same second! So the problem could be only in
a, MAPPING (not very possible - tests take few seconds)
b, in sending IDoc
But what could be wrong?? What could take so many resources??
To the header mapping: I have deleted the Ad Spec Ids and added the header mapping (sender service, receiver service)... But the ALE error was there again!
Honestly, I have read the header mapping docu, but didn't unterstand it, how could it be useful in this case..
P.

Send IDocs to machines depending of the Organizational Units.

hello,
I want to know if there is a way to send IDocs to a determain machine depending of the organizational Unit or their sub-tree objects.
Imagine, I have 10 organizational Units (10 countries), and I want to send to each country without sending the modification to the rest os the other countries.
I there a way I can do it?
Thank yu very much in advance...
PM

Hi David,
This can be done in the Mapping.. For this Java Mapping will be easier.
First you need to read input xml document, and search for the Geography/Region.. And then gorup the similar one into the list etc..
After this Mapping, you will be having one message for each Geography . For this you required to use BPM and in the BPM you can split the messages(1:N) mapping.. But it is still based on the target Structure. If you have many geographies, then it is not an idle solution..
If you want to make your scenario as an Independent, then you can go with some workaround solutions like this. Output all the files into one folder in XI. And from XI execute an Shell Script, which will read the data and tarnsfer into required Geograhy/Person etc.
So in this case XI part is almost independent. Only you need to maintain the SHell script..
This is just my views
Use SAX parser for the Java Mapping here..about Java mapping
Java Mapping
Java Mappings for XI
Mark helpful answers
Hope this helps,
Regards,
Moorthy

Sending Idocs from SAP-R/3 to XI, bundle and map them to one XML-file

Hi All,
We need to send IDoc's (DEBMAS06) from R/3 to XI and bundle and map them to a single xml-file. Please help us with your suggestions on how to proceed using a simple solution (probably need of BPM).
Regards,
Theo

Hi Theo,
there is an example in SAP Library: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm">Collecting and Bundling Messages - One Interface</a>. Plz post us your detailed quetions.
Regards,
Udo

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

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

Sending IDOC's to many partners

Similar Messages

Maybe you are looking for