Port Configuration EDI/IDoc

Please anybody can explain me in detail Port Configuration for EDI/IDoc(T Code WE21).
please explain how can i create new port.
it's urgent please.
thanks
RP

rp
check the following links
http://help.sap.com/saphelp_47x200/helpdata/en/af/7e844367c24d4a950df3205052769d/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm

Similar Messages

EDI IDOC Configuration steps

Hi,
Can anyone provide me the step by step configuration of EDI IDOC ofr both incoming and outgoing mainly for PO.
Thanks
Regards,
Srivatsan

hi,
Refer SAP Note No. 455140
Refer SAP Note No. 546147
Refer SAP Note No. 607108
Refer SAP Note No. 779972
May be it will help you
Thanks & Regards,
Kiran

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

How to file data from sap server to third party-tibco using EDI-Idoc?

Hi all,
I need to send data from sap server to third party system in th form of file.
Please guide me how to send data file from sap server to third party-tibco using edi-idoc?
Also guide the configuration ti be done for EDI.
Thank you.

1)create file port
2)TCP-IP RFC destination with a program RFCEXEC to be executed on application server
3)Dummy distribution model
4)Partner pofile of type other han LS

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
ALE
ALE
Triggering OB via Change Pointers:
 When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
 To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
 Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
 WE20 - Manually maintain partner profiles
 BD64 - Maintain customer distribution model
 BD71 - Distribute customer distribution model
 SM59 - Create RFC Destinations
 BDM5 - Consistency check (Transaction scenarios)
 BD82 Generate Partner Profiles
 BD61 Activate Change Pointers - Globally
 BD50 Activate Change Pointer for Msg Type
 BD52 Activate change pointer per change.doc object
 BD59 Allocation object type -> IDOC type
 BD56 Maintain IDOC Segment Filters
 BD53 Reduction of Message Types
 BD21 Select Change Pointer
 BD87 Status Monitor for ALE Messages
 SALE Display ALE Customizing WEDI - ALE IDoc Administration
 WE60 - IDoc documentation
 SARA - IDoc archiving (Object type IDOC)
 WE47 - IDoc status maintenance
 WE07 - IDoc statistics
BALE - ALE Distribution Administration
 WE05 - IDoc overview
 BD87 - Inbound IDoc reprocessing
 BD88 - Outbound IDoc reprocessing
 BDM2 - IDoc Trace
 BDM7 - IDoc Audit Analysis
 BD21 - Create IDocs from change pointers
 SM58 - Schedule RFC Failures
EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
 A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
 It defines the characteristics of data being exchanged with the business partner.
Partner Function:
 Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
 The type of your business partner .
 EDI KU/LI
 ALE -- LS.
Archiving:
 -Need to archive the important transmitted document
-Created in SARA
 -Assigned in WE20.
PartnerProfile Tips:
 RSECHK07- Consistency check for Partner Profile.
 If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
 To move partner profile to production system choose Partner -> Transport
Port defintion:
 It defines the medium through which data is exchanged between systems.
 tRFC - Used by ALE
 FILe - Used by EDI
 R/2 system system port For R/2 system
 Internet port - to connect with internet applications
 It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
 Output controller
 A service program for determining the output type
 To generate and manage various outputs from an application and control their medium and timing of exchange.
 To retransmit the document without duplicating it
Procedure:
 A procedure defines a set of possible outputs for an application
 There may be more than one procedure but only one can be active
 Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
 The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
 Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
 Represents a business function
 Technical structure is the IDoc type
 Or can say an instance of IDoc.
IDoc :
 They are containers used to exchange data between any two process.
 It represents an IDoc type and IDoc data
 IDoc type is structure and IDoc data is an instance of it.
Pls reward if helpful.

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

Interface between sap to non sap using edi idoc

hello abaper's,
                     i have requirment on creating Interface program for downloading files(PO) from Non-sap system to sap system using EDI Idoc techniques.pls give me a good tips for this requirment..
With Regards
MurugeshRajeev

Hello,
        First of all, we'll need to identify as to what we want to do with the PO Data. For example, If we want to Create Sales Order, there is already a Posting Program available with the Name IDOC_INPUT_ORDERS (FM). This is useful for Creating a Sales Order automatically whenever a PO IDoc is received.
Here is the Information for processing Standard IDoc.
1. WE30 - ORDERS05 - IDoc Type
2. WE31 - Segment Definition for the IDoc Type
3. WE81 - Logical Message Types (ORDERS)
4. WE82 - Assigning the Message Type to IDoc Type
5. WE42 - Define Process Code
6. BD51 - If you want to Code a Custom Function Module,
              then after creating it, you need to register the same
              Function Module in this Transaction Code.
7. WE57 - Assign Message Type / IDoc Type / FM group.
8. WE20 - Partner Profiles
9. WE21 - Port Definitions
Hope this information was helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Configuring EDI Feature failing for BTS2k9

Any pointers to fixing this solution will be greatly appreciated.
OS:Win2k8R2
BTS2k9
Thanks
[10:37:00 AM Error Configuration Framework]Feature: [BizTalk EDI/AS2 Runtime] Failed to configure with error message [<Exception Message="Failed to configure BizTalk EDI functionalities." Source="Microsoft.BizTalk.Configuration.EDIAS2.EdiHelper"
HelpID="StrFailedToConfigEDI"><Exception Message="Failed to add a resource to a BizTalk application using BtsTask.exe." Source="Microsoft.BizTalk.Configuration.EDIAS2.Utility" HelpID="StrFailedBtsTaskAddResource"><Exception
Message="Failed to execute process: C:\Program Files (x86)\Microsoft BizTalk Server 2009\btstask.exe." Source="Microsoft.BizTalk.Configuration.EDIAS2.Utility" HelpID="StrFailedToExecuteProcess"><Exception Message="Microsoft
(R) BizTalk Application Deployment Utility Version 3.8.368.0
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Information: Adding resource (-Type='System.BizTalk:BizTalkAssembly' -Luid='Microsoft.BizTalk.Edi.BatchingOrchestration,
Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35') to application 'BizTalk EDI Application'...
Serialized BizTalk assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
from 'C:\Program Files (x86)\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Edi.BatchingOrchestration.dll'.
Information: Validating resources (count=1)...
* Validating resource (-Type='System.BizTalk:BizTalkAssembly' -Luid='Microsoft.BizTalk.Edi.BatchingOrchestration,
Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35')...
Information: Performing change requests...
Information: Calling BeginTypeChangeRequest for all selected resource types...
PerformingBeginChangeRequest
Updating
resource (-Type='System.BizTalk:BizTalkAssembly' -Luid='Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35') in store.
Information: * Performing change request on type 'System.BizTalk:BizTalkAssembly'
(count=1)...
Information: Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' is not used by any other assemblies. Skipping pre-update operations.
Information:
Updating assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'...
Information: Reading binding information for assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
Information: Successfully selected binding information.
Information: Saved binding information to XML file 'C:\Users\administrator.EDITPS\AppData\Roaming\Microsoft\BizTalk
Server\Deployment\BindingFiles\~Microsoft.BizTalk.Edi.BatchingOrchestration_3.0.1.0_neutral_31bf3856ad364e35.BindingInfo.xml'.
Information: Updating binding information.
ConnectionString='Data Source=10.150.93.220\node2;Initial
Catalog=BizTalkMgmtDb;Integrated Security=True;Enlist=True;Application Name=Microsoft.BizTalk.ApplicationDeployment.Engine'
Information: Updating send ports, send port groups, and receive ports...
Information: Updating parties
and enlistments...
Information: Updating orchestration bindings...
Information: Successfully updated binding information.
Information: Deploy server='10.150.93.220\node2' database='BizTalkMgmtDb' assembly='C:\Users\administrator.EDITPS\AppData\Local\Temp\2\BT\PID1704\BizTalkAssembly\177a8c897a18d9a802d64909374b950a\Microsoft.BizTalk.Edi.BatchingOrchestration.dll'
Warning:
Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' depends on the following assemblies that must be installed in the Global Assembly Cache for runtime to succeed:
Assembly
'Microsoft.BizTalk.Edi.BaseArtifacts, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Assembly 'Microsoft.BizTalk.GlobalPropertySchemas, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Error:
Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' references the following assemblies that must be deployed before deploying this assembly:
Assembly 'Microsoft.BizTalk.GlobalPropertySchemas,
Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Error: Deploy operation failed.
''
Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
references the following assemblies that must be deployed before deploying this assembly:
Assembly 'Microsoft.BizTalk.GlobalPropertySchemas, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Error:
at Microsoft.BizTalk.Deployment.BizTalkAssembly.PrivateDeploy(String server, String database, String assemblyPathname, String applicationName)
 at Microsoft.BizTalk.Deployment.BizTalkAssembly.Deploy(Boolean redeploy, String server,
String database, String assemblyPathname, String group, String applicationName, ApplicationLog log)
Error: Deploy operation failed.
''
Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' references the following assemblies that must be deployed before deploying this assembly:
Assembly 'Microsoft.BizTalk.GlobalPropertySchemas, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Information:
PerformingEndChangeRequestsWithRollBack
* Performing EndTypeChangeRequest for resource type 'System.BizTalk:BizTalkAssembly'.
Error: Failed to add resource(s).
Change requests failed for some resources.
BizTalkAssemblyResourceManager
failed to complete end type change request.
Deploy operation failed.
''
Assembly 'Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' references
the following assemblies that must be deployed before deploying this assembly:
Assembly 'Microsoft.BizTalk.GlobalPropertySchemas, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'


Command
failed with 1 errors, 0 warnings.

" Source="Microsoft.BizTalk.Configuration.EDIAS2.Utility" HelpID="StrFailedToExecuteProcess"
SV

Hi SV,
You have already posted this issue 3 years back and the suggestion made their still holds good.
Trouble Installing EDI/AS2 Runtime
Also refer the thread where the user has faced same issue:
BizTalk 2009 Configuration failing in EDI/AS2 runtime configuration
As suggested, could be that somehow the Microsoft.BizTalk.GlobalPropertySchemas
is not recognized by BizTalk when it configured EDI, though the dll still resides in the GAC folder.
Go to BizTalk Administration console and try to manually add the assembly in the resources of "BizTalk Application 1" application. Then try to configure EDI and hopefully this time you will be able to configure it without any problem.
Rachit
Please mark as answer or vote as helpful if my reply does

Issue with inbound EDI idocs

Hi
we are receiving inbound EDI idocs throgh third party. Third party received EDI file having 5000 transactions .
It was transalated same number of idocs text document and posted in SAP. But after 4 hours same file processed in SAP.
Third party saying they sent only once .
Is there any way in SAP file placed two times or one time .
Any table stores this information . we are using TRFC port . I know EDIF12 table but it was not used here.
Any clue on this.
Thanks

HI
ANY Clue on this issue

EDI/IDOC setting

Hi,
Can anybody suggest regarding any EDI/IDOC setting for SD counsultant apart from developer's work?
Regards
Susrikant

Apart from output there is nothing in SPRO, but there is lot to be done in WEDI.
To understand the basic configuration adn teh setup reqmt for IDOCs, EDI, you can go through the following links.
Then you will understand the configurations needed.
http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli
This one is really good, try to complete the book
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Hope this helps.
You can reward if this helps you

Payment throught EDI IDoc to Bank

Hi,
I have created a new payment method to pay customer credit through EDI IDoc. I have tested in F110 (APP), document getting cleared and IDoc also getting created. After this I'm not sure what I need to do.
Kindly tell me the action points with Tcode (if possible). And also please let me know how to make sure the Idocs are reaching the Bank system for payment.
Thanks
Inba

Hi,
The receiver port of the IDOC can be mapped to bank site.
You BASIS team should be able to help you to make this connection.
Regards,
SDNer

Best practise for EDI-IDOC scenario

I want to create a EDI-IDOC scenario for invoicing our customers.
There are 2 options that I can use, create partner profiles of type KU for each of our customer that we will be invoicing or have
a LS for XI and configure the same.
My company has around 400 customers. So incase i chose to go with KU then i have to configure 400 partner profiles right?
Which is the best practice for this scenario?

As stated above, you can use LS partner instead of KU partner. There are, however, some pros and cons to be considered:
1) Post-processing agent assignment. If you have different people working with different customers you can assign them as post-processing agents to the respective partner profiles. If you switch to LS you will need to have only one agent (it might be a group of people though).
2) When you have a separate profile for each customer then the customer number is included in the IDoc control record. This allows to quickly view the IDocs by customer number. E.g. if a customer calls and asks where the heck is my document then customer service could easily see all the IDocs for that customer in WE05, for example, and check what's going on. With LS they would have to dig into the segments for that.
So the business process requirement decides this. If you don't care for any of this you might be even better off using LS instead of KU, because it requires less maintenance.

Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
In the transaction NACE
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Port Configuration EDI/IDoc

Similar Messages

Maybe you are looking for