EDI Integration

Hi BizTalk community.
I am new to BizTalk and I am looking for some references that will guide me through the process of integrating a trading partner from start to finish. I am currently working as a programmer analyst where 90% of my time is developing software. However, we
need to continue with EDI trading partners integration, a task a previous developer left unfinished. I did EDI integrations for a few years, so I am an experienced EDI integrator as well. Thing is that I used another software (Trading Partner PC) for the EDI
translation, I wrote the maps with a product called Mercator Mapping Tool, and used some C# and VB6 programs for the automation. I have researched a lot and I also started reading some BizTalk books, but none goes directly to the point of EDI integration.
Any suggestions would be greatly appreciated.
Thanks in advance.

Hi,
As being new to BizTalk, I would suggest firstly to go through edi video tutorials (total 5 videos) at : http://msdn.microsoft.com/en-us/biztalk/gg153503
And then you can through others for more insight. Links by boatseller and few below :
http://geekswithblogs.net/VishnuTiwariBlog/archive/2009/10/21/develop-your-first-biztalk-edi-project---part-1.aspx
http://blogs.msdn.com/b/biztalkb2b/archive/2009/03/31/help-materials-for-biztalk-edi-as2.aspx
http://msdn.microsoft.com/en-us/library/bb743276.aspx
http://msdn.microsoft.com/en-us/library/bb727695.aspx
Maheshkumar S Tiwari|User Page|Blog|BizTalk
Server : How Map Works on Port Level

Similar Messages

EDI Integration---Using Seeburger Adapter

Hi All,
I have a below requirement.
EDI----->XI--
>SAP and vice versa.
I am new to EDI integration,i would like to know the procedure steps to do the above scenario.
Thanks in advance,
AVR

Hi,
How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005
http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
Handling EDI interfaces using Seeburger BIC modules
Regards,
Priyanka

EDI integration w/WHM??

Hello Guys,
Anyone plz explain EDI integration w/WHM? appreciate quick reply.??
Thanks.
Mohammed.

Hi,
This is an extract from the sap library.
<a href="http://help.sap.com/saphelp_47x200/helpdata/en/52/16b21f543311d1891c0000e8322f96/frameset.htm">Extract Link</a>
You will find more info around this link.
Interface Between the WMS and External Systems
Purpose
The Warehouse Management system (WMS) has an interface (WMS-WCU interface) with which you can connect
Automated warehouse systems, such as warehouse control units (WCU)
Fork lift control systems or carousels
Decentralized warehouse management systems
to the Warehouse Management system.
Integration
The interface allows communication between the connected systems on the basis of the so-called transactional Remote Function Call (tRFC).
Unlike the synchronous Remote Function Call (sRFC), the system saves the data in temporary storage before sending it to the connected system. This leads to the decoupling of application and communication.
Features
Interface between the WMS and external systems (WMS-WCU interface)
On the basis of the WMS-WCU interface, you connect automated warehouse systems such as warehouse control units (WCU), fork lift control systems, or carousels to the Warehouse Management system (WMS).
For more information see Scenarios for Connecting External Systems and Description of the IDocs.
Mobile data entry (LE-MOB) and the SAP console
Using this interface, you can enter data decentrally, for example via barcode readers or character-based radio frequency devices, and transfer the data to the database of your SAP system.
For more information, see Mobile Data Entry.
Decentralized Warehouse Management system
You can interface the Warehouse Management system as a stand-alone component with the SAP system or integrate the Warehouse Management system with any Enterprise Resource Planning system. This means that the ERP system and the Warehouse Management system can run on separate machines. For more information, see Decentralized Warehouse Management.
Hope it gives some idea.
Thanks & Regards
Sadhu Kishore

EDI Integration using PI with third party connectors

Hi Experts ,
I would like to know the extra cost factors associated if going for EDI integration with PI with third party connectors like seeburger .
1. We have NW 2004s ECC installed . Do we need to purchase PI separately? If yes how much will it cost ?
2. How licensing will happen in case of PI ?
3. How much Seeburger will cost ? Is there any sort of AMC associated with seeburger
4. Do we install Seeburger and PI on the same box ?
5. How will be the landscape with Seeburger Instance ?
6. How we will be able to move Seeburger Objects across the landscape ? DEV->QA->PRD
Regards ,

Santosh Rawat wrote:>
> Hi Experts ,
>
> I would like to know the extra cost factors associated if going for EDI integration with PI with third party connectors like seeburger .
>
> 1. We have NW 2004s ECC installed . Do we need to purchase PI separately? If yes how much will it cost ?
Yes your need to but PI separately,its independed product,its not come with ECC.
> 2. How licensing will happen in case of PI ?
Better to talk with SAP Sales team,they will help you with genuine answers.
> 3. How much Seeburger will cost ? Is there any sort of AMC associated with seeburger
Its depends on which See Burger Adapter You are going to use,.
> 4. Do we install Seeburger and PI on the same box ?
Yes ,we need to deploy the seeburger drivers on PI Server.
> 5. How will be the landscape with Seeburger Instance ?
google it,you wil find the answer i am not sure
> 6. How we will be able to move Seeburger Objects across the landscape ? DEV->QA->PRD
As per my knowledge when you develop any interface using seer burger adapter or predefined mappings,its same procedure to transport also.
Regards,
Raj

EDI integration thru seeburger

Hi Folks,
Scenario: ECC sends PO (orders Idoc) 850 to PI and then PI sends to EDI subsystem using seeburger (AS2 protocol).
EDI system has to send PO order acknowledgment 855 to PI and then to ECC.
1) whether Seeburger adapter supports synchronous scenario ?
2) Please suggest some input reg. this.
3)
Is it good for ECC integration with EDI system using PI (ie seeburger),
Please give comments on Pros and Cons (any way Seeburger adapter licence cost associated)
a) in terms of time line with out PI , how it goes?
Thanks in advance
Regards,
Praba
Edited by: Prabaharan Rangasamy on Mar 16, 2010 2:23 AM

Hi,
If you have already PI System in your landscape you can definetly go for ECC ,EDI System integration with PI using seeburger.
Many customers implemented the same integrations.
Wiithout PI ,are you planning to use someother middleware???? if NO,then withput midleware its very difficult integrate SAP System with EDI System.
Regards,
Raj

EBS - EDI Integration using SOA Suite EBS Adapter

Hi, We would be receiving EDI 850 PO document in Oracle B2B. We want to update this EDI 850 document in EBS. We are using EBS Adapter. But we don't have much idea on how EDI method works in EBS. Couldn't find much references for implementation. Pls. provide some details if you have done this before.
Thanks!

Do you have SOA installed and integrated with R12? If not, please see these docs.
Integrating Oracle E-Business Suite 12.1.3 with BPEL in SOA Suite 11g [ID 1070257.1]
Useful Articles for the Oracle E-Business Suite Technology Stack for Technical Consultant / DBA [ID 828157.1] -- SOA/BPEL/Webservices
Integrating Oracle E-Business Suite Release 12 with Oracle BPEL available in Oracle SOA Suite 11g [ID 1321776.1]
Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12 [ID 556540.1]
Troubleshooting and Known Issues for EBS SOA Suite Deployment in R12.1.1 [ID 797596.1]
Thanks,
Hussein

Web / EDI Integration

Dear friends
How are you?
I am developing a high volume, mission critical Web "B2B" Application for Customer
Relationship Management (CRM) on OS - WindowsNT and database - MS SQL 2000 Enterprise.
Future needs include integration with EDI Systems (GentranServerNT, Harbinger
TLE, GEIS, etc.).
Can I request you to please share all relevant information and experience on this
topic?
Thanking you
Sriram (Ram) Peddibhotla

well, anything between 8 and 88 will do.

EDI Integration w/ B1

Where you I find a list of solutions/partners that will integrate EDI w/ B1? Jim

Dear Ashim,
There is no standard functionality of EDI in Business One, that I know of. We have developed an Add-on that supports full EDI functionality and of course most of the EDI standards like X12 or EDIFACT to name a few..
We are using it also as an integration tool capable of exporting/importing any SBO Document to/from any other format like flat files, for example. It is capable of working with User Tables (importing to) and user defined queries .
I'll be glad to provide you with additional information on the functionality,
Kind Regards,
Simon

Error during EDI integration

Hello,
Trying to integrate an EDI message (DELINS) I am getting a number 51 error: "Scheduling agreements were found with differing sales units".
If I check the EDI message the sales units are PCE (ARD line) and in our Schedule agreement (VA33), the sales units are EA.
So easily, it seems that the error is here but, when I try to modify the sales units in the Idoc (WE19) and change PCE for EA in segment E1EDP10 I get a dump.
So any ideas? Somehow it should be possible to avoid this kind of errors asking the system not to check sales units or something like this?
The option of changing the units in the Material Master and then in the Schedule agreement is not my favourite.
Thank you

Hello again,
I've tried changing the unit in the material master, but then after doing all the necessary changes I get a new dump error.
It seems like some kind of incompatibility between the SAP measure unit (EA) and the Idoc measure unit (PCE).
I've also tried changing in the customizing the unit of measures changing the EA ISO code to PCE instead of EA, but then again I get the dump when trying to integrate.
Ideas?
Thank you

Integration Repository objects for EDI adapters

Hi,
We are currently evaluating EDI integration options, and I need some information.
Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
Thanks and Regards
Manish

hi,
>>>>Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
you get them if you buy the adapter
>>>If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
I have one presentation about the seeburger
if you want check my e-mail in my business card
and send me an e-mail
I'll send you this presentation back
Regards,
michal

B2B EDI translation ----Is it possible to increase the sub-element length

B2B EDI translation ----Is it possible to increase the sub-element length??
Am new to the B2B 10g- EDI Integration environment. In our production setup, am getting the following error.
B2B EDI Translation failed, because one of the fields was too long. The length of Sub-element length is '41'. The maximum allowed length is '35'.
In the segment RFF defined in the guideline at position 0070; Is it possible to increase / expand the lenght from 35 to 41.....
Thanks and Rgds,
-Srini

Hi Nitesh
I have the same problem what srini explained above.
I'm using Oracle B2B Document editor.
That corresponding element's field is in disabled state ,a red triangle displays in top right corner of that field.
Could you help me to solve this issue?
Regards
Kathir

3rd party adapter integration into XI

Dear Experts
I wanted to know how 3rd party adapters are integrated into XI?

Hi Dheer,
There many third party adapters available in market.
One example is seeburger:
U need to follow the below steps for integration into XI:
For the same requirement you need to follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
if u need process then let me know I will send u the configuration threads which is required for integration.
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Brief about seeburger:
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
refer belwo weblog:
/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Thnx
Chirag
Edited by: Chirag Gohil on Feb 25, 2008 12:51 PM

SAP to 3rd party: EDI and XI: Needed advantages and disadvantages

HI All,
I have a requirement to sent PO data from SAP to 3rd party Vendors.(more than 30 vendors). Client insists on using EDI.!!
I have completed the config on SAP R/3 side and IDOCS are created in SAP R/3.
Since we have XI in the landscape, I have a few questions in my mind. Appreciate if you could give you feedback on these questions:
1. Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
Thanks in advance.
Regards
Shirin

Hi,
1) Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
A) For EDI integration u need to have the EDi adapters and for that u need to purchase the seeburger license and which is need to be installed on XI and after that only u can use EDi adapter with Xi.
U can not ignore XI.
2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
A) Yes but only when u purchase the seeburger license. there are other ways as well either use conversion agent or module program which convert the XML to EDI format.
3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
A) U have to use the EDI adapters with Xi and configure ur scenario in XI for all the vendors.
4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
A) Seeburger provide As2,X400,FTP,VAn adapters for EDi integration.
5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
A) What EDI format ur vendor receivers the data it depends upon that.
6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
A) Mapping is the part of desing and mapping changes accroding to the business requirement and mapping rule which is provided by Functional people.
7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
A) u need to do the mapping between IDOC and EDi then only the data will be mapped with the required target EDI strcuture.
chirag

Pairing of EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types

Hello,
I am looking to pair the following EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types, for our EDI Integration.
Can some one help me to identify which suitable IDoc type, should I use? Your help is greatly appreciated.
142
824
830
846
853
861
862
864
866
I am not sure, I am seeking the help in the righr forum -:)
Thanks in advance.
Namadev

Hi namadev
Please you can check this link.
http://www.erpgenie.com/sap/sapedi/ansi.htm#Mapping_x12_to_SAP
thanks.

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 Integration

Similar Messages

Maybe you are looking for