Edi connections

EDI: for outbound we will transfer the idoc as a file through file port OK.
But for inbound what is the transaction to get the idoc from EDI subsytem ( simply we have unix directory is mounted to SAP and edi system)
what are the transaction codes we need to process to get the idoc....
Thanks,
Kiran.M
Edited by: kumar m on May 2, 2008 3:48 AM

I hope i understand your question correct:
I this is outbound:;
you can create 2 rfc destinions, create the port manual for this RFC , in the partner profiles you can specify which message should go where;
in the distribution model ( BD64) you can specify filters what should go where.
If this is inbound
just create the partner profiles
Let me know if this is usefull or ifI misundestood the question.

Similar Messages

Maintain outgoing EDI-connection data for partner 199093 during ORDRSP

Hi Experts,
We are trying to send the "Order Confirmation" using "ORDRSP" IDOC message type. So we created the new Output type as ZBA0 (Copy of BA00) and assigned with the sales output pricing procedure.
Then we maintained the "partner profile" in WE20 in the "Outbound" parameter. Then we tried to send the Order confirmation in the sales order. During that time, we are getting the error as "Maintain outgoing EDI-connection data for partner 199093".
After maintaining the relevant configuration and partner profile maintenance also we are getting the above mentioned error message. Kindly give your valuable comments on this issue, which will help us to speed up the process.
Warm Regards,
Nag

Hi Nag,
The message '"Maintain outgoing EDI-connection data for partner 199093" comes if the partner profile settings are not maintained properly.
Please check wehther the customer 199093 is maintained under the partner type KU. If it is maintained, please check whether the message type 'ORDRSP' is configured in the outbound parameters for the customer 199093.
If the above settings are done properly, please check whether the output type ZBAO is configured based on the partner type of the customer 199093.
Hope this solves your problem.
Regards,
Vijaymadhur.

Maintain outgoing EDI-connection data for partner

Dear All,
While creating the output type for a purchase order & selecting the medium EDI system flashes the error message whiah is as below.,
Maintain outgoing EDI-connection data for partner
Kindly help for the same.
Rahul

Hi
You need to maintain this partner field (Partner who receives the output-SystemidCLNT eg..D4JCLNT100) in the create PO output screen. and please maintain the message type in the transaction WE20 for your BP or LS and define the message type for your PO in SPRO.This should solve the problem
Regards
Vinod
Edited by: Vinod Kumar Pedapati on Feb 24, 2009 8:44 AM
Edited by: Vinod Kumar Pedapati on Mar 2, 2009 11:26 AM

PO Change O/P error- Maintain outgoing EDI-connection data for partner for

Hi Experts ,
We are connecting our SAP ECC 6 ( Ehp 4) sytem to 3rd party system via SAP PI. We already done all the settings..line Output detemination procedure, Partner Profile ( WE20) , Port creation , Condition Records..etc.
We have PO Creation ( ZCRE) and PO Change ( ZPOC) Outbound messages to go from our system. Both have sepate message Types, since PO Creation IDOc should go immidiatly ( Dispatch time 4-Send immediately (when saving the application)
and PO Change IDoC should send as per wish manully in ME9F ( Dispatch time -3 Send with application own transaction).
Once PO Created , Output Message successfully triggering and IDoC is creating ( Green Color) ..so it is working fine .
Fo PO Change Message we had selcted Program -FM06AEND & FORM routine -CHANGE_FLAG.
We also set "Multiple issuing " checkbox in the Output Type and no requierment is assigned.
In WE 20, for Logical system ( LS) Partner XYZ, we set Process code ME11 and checked "Change Message"
1. But when I change PO Qty , output is not automaticaly triggering .After changing PO, if we see determination Analysis, in Procedure RMBEF1, this output ZPOC shows 2 times. First, it shows green color,...Output Found , and second times, it displays, "partner XYZ is not an EDI partner"
2. If we try to manually enter the Output ZPOC in PO Header, then system gives the Error - Maintain outgoing EDI-connection data for partner XYZ.
Can anyone pls suggest what should be the reason for above?
Thanks
NAP

Issue Resolved .
The reason for this system behaviour is in fine-tuned control: We was
using ZMIN only for new message output and ZCHG only for change messagesNevertheless, you can maintain two entries in WE20 for ORDCHG:
EF ZCHG ME11 w/o Change message flag
EF ZCHG ME11 with Change message flag
Thanks

IDOC Error - Maintain outgoing EDI-connection data for partner

Hi
I am trying to send customer invoice to an external system thru IDOC, type INVOIC02. I have done the basic setting for the output type ZEDI to transfer the doc thru edi. But when i got to the output types of the doc and give the type ZEDI and the partner, i get the msg "Maintain outgoing EDI for partner".
I have created a partner profile for customer (KU) for the same partner number in WE20 and have given the outbound parameters with the message type INVOIC.
These are the settigns for my partner profile:
part type: KU
msg type: INVOIC
Outbound Options: Receiver port: A000000050 (tRFC)
Packet size: 1
Transfer IDOC immeediately
basic type: INVOIC02
Message Control: Application: V3
Msg type: ZEDI
Process Code: SD09
Following are the steps that I did in VF01
menu GOTO>> Header>> output
I have only RD00 there
I manual add ZEDI there hit return, i get the medium, partner function and partner populated to EDI, SH and the partner number.
i get the msg: Maintain outgoing EDI-connection data for partner 300203.
What other setting should i do to get it working?
Regards
Sujai.

Hello Sujai
In our case we never send any invoice directly to the customer (Ship-to-party) yet to the payer (partner role = 'PY') defined for this customer (check partners in XD03 for Ship-to-party).
The output sent from the invoice is in our case:
- output = 'ZRD0'
- medium = '6' (EDI')
- function = 'PY' (payer)
- partner = <partner number of payer>
The partner profile (WE20) looks like this:
- partner no = <partner number of payer>
- partner type = 'KU' (customer)
- partner role = 'PY' (payer)
Regards
Uwe

Maintain Outgoing EDI Connection Data for Parter

We need to send Debit and Credit Memo to customers via EDI?
How to maintain Outgoing EDI connection data for parter?
and
How to see the outgoing EDI connection data for partner which is maintained already?
and
How to maintain EDI partner agreement?

You can maintain EDI partner data thru transaction WE20.
Thanks,
Manish

EDI connection

Hi all,
Can anyone let me know that How I can Maintain outgoing EDI-connection data for partner xyz ?
Thank you.
Regards

Hello ansix12 or anyone,
I have been requested by my bank to set up EDI for their MT940 EBS...
I know what I need to do in terms of config - partner bank id..ale configuration, etc etc
What I really don´t know, and the client requested me this, is what to request to the bank?
Is the only thing the bank needs to do is place the txt files in a server directory and communicate it with a SAP directory?
The idoc construction is then made in SAP from the received bank file?
Thanks for any inputs on this as I don´t know so well the steps before geting to SAP.
Alexandra

Error:maintain out going EDI Connection for Partner 1000

Dear Gurus,
I have output master record for vendor 1000 and i have done edi settings namely fileport, partner prifile. My problem is
1While creating PO, the settings are not reflected ( i checked them in Path Goto->mesages.) When i try to give them manually the erros says"MAINTAIN OUTGOING EDICONNECTION FOR PARTNER 1000"
Please let me know how to correct it.
Regards
Rao

HI Mano,
Make sure to create entries for output control as well as for outbound parameters.
XXXX is defined in the partner profile by WE20.
To this XXXX partner, there are two setup are needed to solve the issue in WE20:
1 . Partner Role is required ( like LS for Logical system).
2. in Message Control tab, an Apllication/Message Type/Process code record is required as well. The message Type is actually the output type.
Please check these and post if it is not resolved.
Regards,
Madhu.
Edited by: madhurao123 on Jun 24, 2011 8:47 AM

Multiple EDI Connections from ECC

Hello All,
Could you please let me know is it possible to create 2 ALE connections in 1 system and then choose as per partner profile which connection to be assigned?
Regards,
Anand

I hope i understand your question correct:
I this is outbound:;
you can create 2 rfc destinions, create the port manual for this RFC , in the partner profiles you can specify which message should go where;
in the distribution model ( BD64) you can specify filters what should go where.
If this is inbound
just create the partner profiles
Let me know if this is usefull or ifI misundestood the question.

Problem in sending purchase order via EDI

Hello Experts ,
I want to send purchase order via EDI , for this i have refer the below link for configurations.
link :
http://help.sap.com/saphelp_nw04/helpdata/EN/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm
I have created purchase order (ME21N)and saved it.
Then i went to ME22N , Goto -> Messages, i am getting below error .....
Maintain outgoing EDI connection data for partner 8888(this is the partner number i have created in partner profile)
please suggest the possible cause of the error and how could i rectify it.
Thanks
Sonal

Ensure that you have the relevant message type in outbound parameters for this partner profile

Purchase order distrubution using EDI

Hi, SAP gurus!
I am trying to set up Purchase order distrubution using EDI. ORDERS idocs will be sent through middleware message broker. I added ORDERS idoc in LS partner profile outbound data and set up medium type 6 for PO output. Something else is missing since I can't add manually output to a purchase order - error message VN032: "Maintain outgoing EDI-connection data for partner"
"Short Text
Maintain outgoing EDI-connection data for partner &
Diagnosis
The system could not locate the EDI partner agreements (outbound) for partner .
System Response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner . Make sure to create entries for output control as well as for outbound parameters."
What else is needed besides outbound idoc data in partner profiles?
Maybe I have to do everything completely different?
Thanks!

If it's an EDI interface, you should be using a trading partner partner profile type (KU or LF) ... a customer or vendor ... not a logical system, although you can use LS it's not really an optimal solution and you need to create more generic configuration to generate your IDocs from your business documents.
I cover configuration of output control for outbound EDI invoices in a series of blog postings at:
http://it.toolbox.com/blogs/ehadzipetros/dazed-and-confused-output-control-ate-my-brain-33944
http://it.toolbox.com/blogs/ehadzipetros/no-longer-dazed-and-confused-my-brain-finally-ate-output-control-34065
http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-contented-glow-34232 and
http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-bringing-it-all-together-34416
I also cover it extensively in my new book from SAP Press "Architecting EDI with SAP IDocs". All steps are covered in the blog postings and the book.
Good luck.

Settings for edi

Hi
what r the settings needed in sap system for transferring the idoc to edi subsytem?
is the ale settings require for edi connection?

1. EDI Subsystem is not the only way to translate EDI message into IDOC, these subsystems are typically very costly. When you are not using heavy duty EDI processing, you can even use ABAP to translate EDI message. This turns out to be more cost effective for low volume.
2. I don't see any value in uploading this information into a Z-Table. If it is an EDI message, chances are there must be a way to post this information into SAP which can be used for adding value to the process.
3. You must pay attention to the naming convention of the files, as you will need to make sure that you are not processing the same message again. Also it is a good practice save the files into another directory (archive directory).
4. You can ask your EDI partner to trigger an event in SAP (You can give them a batch file which runs program sapevt to do that). It helps if you want real time interface, but scheduled job as you are thinking will also do the job.

EDI Output type

Hi guys
I have configured the EDI output type in the system and assigned to the procedure but when i am creating the sales order the system is not picking the procedure and when i pick it manually and try saving then it gives me error "Maintain outgoing EDI connection data for partner". I am manitaining records in VV11
Where do i maintain the connection data???

Hi,
RFC Destination : SM59
Partner Profile : WE20
Port Definition : WE21
Go through the following links:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sapgenie.com/sapedi/index.htm
Hope this will help.
Regards,
Naveen.

EDI Output Type error

Hi,
I have an output type ZSVC for sales contracts of a type. When I try to assign the output type ZSVC before saving the sales contract, I get the following error,
Maintain outgoing EDI-connection data for partner
Any idea what it could be. I have maintained the partner profile for that customer, with the requisite data.

Maintain outgoing EDI-connection data for partner
Message no. VN032
Diagnosis
The system could not locate the EDI partner agreements (outbound) for
    partner .
System Response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner . Make sure to create
    entries for output control as well as for outbound parameters.
This is the error I get again and again. I have however maintained the partner data in SPRO EDI Partners - >
Any bright idea guys...

EDI & IDOC Configuration

Hi Friends
Any body please help me to my questions.
1) How to configured to EDI (Send idoc to third party Aramex).
2) What is the process code for Betmas01 IDOC.
3) How to raise idoc automatically when we create a data on sitemaster. (Betmas01).
Thanks
Krishna

Hi krishna,
welcome to SDN
Configuring EDI Integration
BEA WebLogic EDI Integration must be completely configured before it can be used. Because EDI Integration depends on BEA EDI Connect for WebLogic Integration to operate properly, make sure you configure Power.Enterprise! correctly so that you can communicate with your trading partners.
General Configuration
This section discusses the general configuration information that you should perform before attempting to configure a specific document exchange with a trading partner.
Configure Trading Partners
Before configuring individual transactions, you should configure all trading partners, including your own company, using Power.Manager!. For more information about configuring trading partners, see the following topics:
Configuring Trading Partners
Chapter 4, "Partners," in the Power.Manager! User Reference Manual
Configure VAN/Trading Partner Connectivity
You should also configure your trading partner connectivity before attempting to configure individual document exchanges. See the following topics:
Connections and VAN Connectivity
Chapter 3, "Connections," in the Power.Manager! User Reference Manual
Although you may not want to set up connectivity to your production trading partners at this time, you may want to configure them with file connectors for development and testing purposes.
Configuring EDI Integration to Receive an EDI Document
This section describes how to configure EDI Integration so that the BEA WebLogic Adapter for Power.Enterprise! 3.1 can receive an EDI document and send it to the WebLogic Integration process engine as an XML document.
Pre-Planning
Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide any export utility to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You will be responsible for creating both the DTD and XSD files.
Within Power.Enterprise!
Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
Mapping XML and EDI Data
Chapter 3, "Maps" in the Power.Map! User Reference Manual
Define an inbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
Define an RMI target connection. This connection is used to communicate with the WebLogic Integration process engine.
Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. This exchange profile should connect the inbound connection from your trading partner to the RMI target connection.
Within BEA WebLogic Integration
Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise!.
Create an event for the application view you just created, using the procedure in Configuring Events. Be sure to set the following parameters:
Event Name: A descriptive name for the event, such as ReceivePurchaseOrder
Event Description: Text that provides details about the event
RMI Service Name: Should match RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section
XSD: The XML schema of the XML message to be received (optional)
XML Root Element: The XML root element of the XML schema (optional)
Deploy the application view you have created and defined.
Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
Note: Always start the Power.Server! before you start WebLogic Integration or WebLogic Server. The WebLogic Integration connectors expect to see the Power.Server! running when they are initialized, and they throw exceptions if Power.Server! is not running when they are initialized.
Configuring EDI Integration to Send an EDI Document
This section describes how to configure EDI Integration to send an EDI document using an XML document in the WebLogic Integration process engine as the source.
Pre-Planning
Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide an export utility that can be used to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You are responsible for creating both the DTD and XSD files.
Within Power.Enterprise!
Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
Mapping XML and EDI Data
Chapter 3, "Maps" in the Power.Map! User Reference Manual
Define an outbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
Define an RMI source connection. This connection is used to communicate with the WebLogic Integration process engine.
Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. The exchange profile should connect the RMI source connection to your trading partner's outbound connection.
Within BEA WebLogic Integration
Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise! in this document.
Create a service for the application view you just created, using the procedure in Configuring Services in this document. Be sure to set up the following parameters:
Service Name: A descriptive name for the service, such as SendPurchaseOrder
Service Description: Text that provides details about the service
Connection Name: Should match the RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section.
XSD: The XML schema of the XML message to be sent (optional)
XML Root Element: The XML root element of the XML schema (optional)
Deploy the application view you have created and defined.
Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
see this link for complete edi information
http://msdn.microsoft.com/en-us/library/bb246069.aspx
for your second question......
sapsdforum.files.wordpress.com/2008/03/idoc_handy_doc.pdf
Assigning a Process Code (Direct Inbound Processing)
This section describes how to assign a new process code to the new function module. This enables the function module to be identified from the partner profiles defined in the IDoc Interface when an IDoc of the new message type is received.
Prerequisites
You must have completed the required steps in Defining and Using a Basic Type .
Procedure
Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Development ® Inbound Processing ® Process Code (WE42), or navigate to Inbound Processing Process Code, then and New Entries.
Enter your process code and a description. Choose the Processing with ALE and Processing by function module options and save your entries.
The maintenance screen is displayed (either automatically or manually), in which you can assign the inbound function module to the process code.
Choose New entries and enter in the detail screen:
Your process code
Module (inbound) frame: Your function module and the maximum number of attempts permitted for posting the application data before exception handling is triggered.
IDoc frame: Your object type, the trigger event inputErrorOccurred and the completing event inputFinished.
Application object frame: Your object type
Leave the other fields blank. Save your entries and return to the process codes inbound initial screen.
Go back using to maintain the inbound process codes and choose the Logical message navigation.
In change mode choose New Entries.
Enter the message type (logical message) and the process code and save your entries. As a result, the possible entries (F4) in the partner profiles can display the possible process codes from the logical message, that is, the business view.
If you chose all types in the last step, the value help displays the process code for all message types. This is also valid for both other options for message type and function.
Result
This assignment has specified a new process code for the function module. You can now enter this process code in the partner profiles.
Make the following entries for the example:
Process code
TESTEIN
Basic type
TESTER01
Function module
IDOC_INPUT_TESTER
Maximum number of attempts
0
Message type (logical message)
TESTER
IDoc object type
IDOCTEST
Application object type
BUS2032 (sales order)
To generate Partner profiles automatically you may use BD82 or go to BD64
thanks'
karthik

Edi connections

Similar Messages

Maybe you are looking for