EDI Subsystems vs XI - functional differences

I have seen from posts in this forum and other resources that it is possible to use XI as an EDI subsystem (please correct me if that is incorrect). However, what I would like to know is what functionality is missing if you do that.
Also, I thought that it was the responsibility of the EDI subsystem to update the status of the IDocs as appropriate. If true, does XI also do the same thing?

Hi Praveen,
I have been working with IDocs for a few years now, and from what I understand, it is the responsibility of the EDI subsystem to update the status section of the IDoc (the EDIDS status record); you know, status such as
18 - Triggering EDI subsystem OK
22 - Dispatch OK acknowledgement still due.
So does XI actually update the IDocs with this status information?
The point is: if I use XI as an EDI subsystem, and it doesn't do that, I cannot tell what has happened to the IDoc when I use the R/3 reporting tools to check the status of all the IDocs.
I know that XI has its own message monitoring built in, but I still haven't had a clear answer regarding updating of IDoc status per se.
Kind Regards,
Tony.

Similar Messages

IDOC : error message 20 : Error triggering EDI subsystem

Hi,
I am creating an extended idoc for WP_PLU message type . I am sending the data from my LS to KU(Customer).
In WE20, I have configured the message type for that KU. I am using an XML port .
The problem is that the Idoc file is getting created properly but it is thowing this message : Error 20 : Error triggering EDI Subsystem.
In WE21 , I have ticked the Start subsytem radiobutton. I am not using any Middleware.It is simple data transfer .
Same thing is working file when I am assigning a File port instead of XML port.
Please help me on this urgently.

Dear All,
Many thanks for all suggestions. Very appreciated it guys.
My problem solved, the issue was actually from the Functional configuration.
After debugging i found out that there's a option to generate a trigger file (related to POS Outbound). If you tick this option then maybe you have to maintain the download path somewhere.
My case is the option was ticked but system can't find the path.
SAP put as error message 20 in the IDOC status.
This maybe can explain also why i still can see my IDOC reached XI and file generated. Since the issue is not really related to any setting in IDOC but more to business configuration.
Best Regards,
Victor.

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

How to find if there is an EDI Subsystem?

I am working with an SAP Partner who is having problems setting up an IDoc Listener in SAP-MII. After troubleshooting the errors in the configuration, I run into one which I can't seem to resolve. During the configuration of the Partner Profile (WE20), we are instructed to use Agent 50010120. According to the partner the error message is as follows:
Object type O, ID 50010120 unknown (please observe upper/lower case)
     Message no. E0624
Diagnosis
     Object 50010120 of type O is not known in the system.
Procedure
     Enter a valid object and check the type.
     Make sure upper case and lower case are used correctly.
Any thoughts as to what can cause this problem? I have done a number of these IDoc Listeners in MII and never ran into this problem before. Is it an indication that an EDI subsystem is not installed or if installed, incorrectly configured?
Thanks for your help,
Mike

It's been a long while ago for me, but this sounds like you're trying to assign an organizational unit that does not exist.
Either the value 50010120 is not correct, then use a different one, or it has to be set up in org managment (tx PPOME). Due to internal numbering, it might very well be the first option.
Thomas

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )
Keeping the above fatcs in mind could you please tell me how to remove the error with status 20 "Error triggering EDI Subsystem".

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

What are the functional differences between the iPhone and the iPod Touch, barring of course the differences in service requirements.

What are the functional differences between the iPhone and the iPod Touch, barring of course the differences in service requirements.

For one, their form factors are slightly different as the iPhone has a bit more squarish body whereas the iPod Touch has a tapered back to it.
The iPhone also has much better front and rear cameras. Exact details as to the difference in megapixels depends on whether or not you talking about the iPhone 4 or 4S. If you would like to get more details, you can always view
each models specs on Apple's online store.
See here for a better explanation.
http://en.wikipedia.org/wiki/IPod_Touch#Comparison_to_the_iPhone
I'm sure others will chime in with other things as well.
B-rock

Key functional differences between SRM 7 and SRM 5

Dear All,
I urgently need to put togther a comparison document thst list key functional differences between SRM 7 and SRM 5.
NB. i donot have access to service marketplace.
sheena.roberts(AT)yahoo
Thanks
Edited by: Sheena Roberts on Jan 18, 2011 11:21 AM

Hi Sheena,
Go to difference between srm 5.0 and 7.0
Regards
Vishal Pd

Interface/Functional Differences between EPM Planning 11.1.1.3 & 11.1.2.2.

We are considering a migration from Hyperion Planning 11.1.1.3 to 11.1.2.2 and have found lots of documentation describing the technical exercise but little on the functional differences between the two products that would be of more interest to our users.
Q1. Will 11.1.2.2 appear to our users as fundamentally a different product requiring retraining, changes to business procedures etc?
Q2. Is there any documentation out there that compares the functionality and 'look' of the two releases that I have missed and that would help?
Thanks.

You could have a look at the cumulative feature tool which highlights functionality additions between versions by product - https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1092114.1
It is probably worth setting up a quick 11.1.2.3 POC planning instance to have a look at the new version of planning to see whether you feel that additional training will be required - http://docs.oracle.com/cd/E17236_01/epm.1112/epm_planning_rapid_deploy_1112200.pdf, the main change is the look and feel with the ADF functionality the concept of planning has not changed, the ADF functionality can be switched off if you want to revert back to the old style.
Cheers
John
http://john-goodwin.blogspot.com/

20:Error triggering EDI subsystem

Dear All.
I am tirggering IDOC with standard t-code(WPMA) from SAP to middleware( It provides Sap Adapter ).
1) I have created TRFC port (SM59).
2) Defined the port(WE21)
3) Defined the Partner Profile(WE21) Outbound IDOC TYPE: wp_ean01
then, I tirgger IDOC with WPMA.
but , the status is :
       20 Error triggering EDI subsystem
       03 Data passed to port OK
            IDoc sent to SAP system or external program
       30 IDoc ready for dispatch (ALE service)
            Receiver exists , No filters , No conversion , Version conversion
        01 IDoc generated
It is strange that the middleware can receive the data which I send.
What is the problem?

Hi Peter.
First        : The RFC destination is OK, I can test it , the middleware can receive
                 the IDOC data.
Secondly : I define the port(WE21: Transcation RFC).there is another port
                 ( file port) in SAP, but I do not think it can trigger the processing.

Error triggering EDI subsystem

Hi ,
I am getting error - Error triggering EDI subsystem- while posting Idocs in R/3 to XI.
But messages are reaching XI and final XML files also getting generated in outbound location, no issues.
I AM USING PARTNER PROFILE OF TYPE - KU(CUSTOMER)
Following are the status messages i could see in R/3 (tran code-WE05):
20 Error triggering EDI subsystem
03 Data passed to port OK
IDoc sent to SAP system or external program
30 IDoc ready for dispatch (ALE service)
Receiver exists , No filters , No conversion , Version conversion
01 IDoc generated
Please suggest me how to get rid of this error.

Hi Rajesh,
Check the ports (we21), RFC destinations, Partner profiles are defined correctly or not.
Regards
Kannaiah

Error triggering EDI subsystem : Error#20

Getting error 20: Error triggering EDI subsystem while triggering IDOC for XI. But, messages are getting posted into XI and final XML files also getting generated in outbound location.
I am using partner profile of type customer in R/3.
Following are the status messages I could see in WE05.
20 Error triggering EDI subsystem
03 Data passed to port OK
IDoc sent to SAP system or external program
30 IDoc ready for dispatch (ALE service)
Receiver exists , No filters , No conversion , Version conversion
01 IDoc generated

Rajesh,
While creating the Partner Profile, have you added something in the EDI Standard tab?
By default if the requirement is only to post an idoc to Xi, you need not add anything to the EDI standard tab for your outbound Idoc entry in We20.
Regards
Bhavesh

Functionality differences between Principal Toolbox & Ms Projects 2010

Hi there,
I'm looking for some advise about the functionality differences between Principle Toolbox (planning module) & MS Projects 2010.
Currently I'm working at an IT company where my project managers use MS Projects 2010 to plan their activities for their projects.
My management wants to know what the differences in functionality are between the two programs. I'm not looking for answers like "different GUI", but (for example) I would like to know what functionalities can you use with MS Projects and can not
use with the Pincipal toolbox.
I hope someone, who has experience with both programs, can give me some good advise.
Thanks in advance

Hi,
I've never worked with Principle Toolbox but here are 2 interesting comparisons which you might already know:
http://project-management-software.findthebest-sw.com/compare/3-21/Microsoft-Project-vs-Principal-Toolbox
http://www.itqlick.com/index.php?module=Products&pname=internalcompare&prod1=112&prod2=2395
I think the main concern should be that Principle toolbox doesn't offer a cloud solution.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

IDOC Error Status 20 - Error triggering EDI subsystem

Hi Expert
I have articles which have 2 different EAN, (KG & EA) for single store i am getting error , if i generated a IDOC for EA articles, not KG articles.
Kindly suggest me a solution
Regard
Nabil

Hi,
Please check with this link, it could be helpful.
Error in idoc with status 20 "Error triggering EDI Subsystem"

Error Triggering EDI Subsystem 20

When we try to send IDOCs from SAP to XI system using WPMI transaction, we are getting status 20 ( Error Triggering EDI Subsystem).
What should be done to overcome this issue?
Regards
Raj

Hi Rajagopal,
This thread solves your question...
Error in idoc with status 20 "Error triggering EDI Subsystem"
Can you please check if the PORT and LS details in the control record are correct
cheers
Prashanth
P.S Please mark helpful answers

Replacing EDI subsystem with SAP XI

Hi Everyone,
I have a scenario in place where i want to replace the EDI subsystem with SAP XI.
I know that using Content Master is one of the solution but i have also heard that Content Master is having some license issues. Now after Content Master what is the next best solution for parsing the EDIFACT and X12 format files.
Thanks and Regards
Rahul Nawale

Hi Rahul,
SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
Have a look at these links:
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
For more i would suggest you to go through these links:
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI.
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
There are also a few ways to use EDI with the ALE system of R3.
inbound EDI to R3
1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
outbound ALE message from R3 to EDI system
1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
have a look at this example:
http://www.ean.se/EANCOM%202000/iftmin/example.htm
Details on how to configure can be found on SDN
I hope this helps....
Regards,
Abhy

EDI Subsystems vs XI - functional differences

Similar Messages

Maybe you are looking for