XI vs Idocs system

hi
i use a software on OS400 who do some data transfert with SAP R3 versions 3 or 4 (4.6C for example). We receive and sent IDocs with RFC protocole.
How works XI, what the difference with old IDocs system. how do new data transfert between SAP and OS software with XI ??
thanks a lot, i'm a noob in this )))

Hi,
To connect to SAP R3 using XI there are two ways through RFC or IDOC.
When data is sent from RFC or as a IDOC to XI,then XI converts that RFC message to XML format and then forwards it to receiver system(whether SAP or Non SAP)
Similarly in case of IDOC XI converts that IDOC to IDOC XML using R3 IDOC Metadata and then forwards the same to receiver system whether SAP or Non SAP.
To transfer data from or to XI again we need RFC destinations to be created on Server side or R3 side.
Thanks.

Similar Messages

BPM - IDOC System Acknowledgements from R/3

Hi My scenario is File-XI/BPM-R/3(Idocs).
In Integration process, we configured 'system ack' in Send Step which sends Idocs to R/3 system.
BPM Process stays in 'STARTED' state forever though XI received acknowledgement ( in SXMB_MONI, on the main screen ACk Status is in '?'mark meaning its still waiting for Acknowledgement. But the moment you click on the message Ack status becomes 'Ack received' and BPM ends".
This seems to be a bug.
How can the Acknowledement staus changes the moment you clike on the message?. Does anyone have same issue?. Any suggestion will be appreciated. we are on PI7.0 sps6.0 environment.
<b>we donot want to deal with ALEUPD..so please do not suggest to config ALEUPD.</b>

HI,
see the below
The Business Process Engine supports Acknowledgments when sending asynchronously as follows:
Acknowledgment------     Processing of Send Step
Receiver system does not support requested acknowledgments ---     Send step completed successfully
Positive acknowledgment----
     Send step completed successfully
Permanent negative acknowledgment------     Send step triggers system error for which you can define a specific exception handling.
Temporary (transient) negative acknowledgment-------     Send step continues to wait because the temporary acknowledgment can still change to a permanent or negative acknowledgment. This can occur in the IDoc environment in particular, for example, when a user intervenes.
Exception or error handling within the integration process is not possible. However, using message monitoring you can determine whether the acknowledgment is temporary or not.
Acknowledgment with multiple receivers     A message sent from a send step can have multiple receivers. In this case, the system duplicates the message accordingly. Acknowledgments returned from the respective receivers are ignored and the send step continues to wait.
If multiple receivers are possible and you want to evaluate the individual acknowledgments, you must define the integration process accordingly. To do this, determine the receivers in a receiver determination step and send the message to the individual receivers in a loop.
For more information about acknowledgments, in particular how they are used in the adapter environment,
Note: see SAP Note 837285.
Regards
Chilla

In IDoc system is picking Plant code instead of Ship to party.

Hello Experts,
I am not so good in Idoc process.
When I am reprocessing the IDoc I came to know that system is picking Plant code (plant address) instead of Ship to party code.
Kindly let me know How can I check it ?
How I can reprocess it ?
is there any way/t-code we can track the mapping in Idoc ??
Awaiting your precious reply.
Thanks,

Hi,
Please provide your scenario
because Message type and Basic IDOC type varies from process to process
if you know Message type, check in WE41/WE42
and underneath you can get logical message as well

IDOC - system requirements

Hi,
I am not sure if this is the right forum for my question, sorry if it isn´t.
I want to get some really basic informations about SAP and IDOC. Can anybody provide me with a source or the info what system requirements a SAP-System has to use the IDOC-technology? Do I need a special configuration / module for this?
Also a source for further information what kind of use-cases for IDOCs exists (a few examples where and for what I could use IDOCs would be great for better understanding).
Sorry for these really basic questions, I am not really familiar with the architecture of SAP in this case.
Thanks a lot for your help,
Christoph

Hi Cristoph,
Welcome to SAP
Basically an IDoc stands for Intermediate Documents, these are the documents with the help of which data is exchanged between SAP R/3 and non-R/3 systems.
To know more about IDoc check this link http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Also if you are new to SAP IDOC or ALE check the help.sap
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
And the ERP forum will be the most correct forum for your query
Enterprise Resource Planning (SAP ERP)
and if you have some IDoc development queries raise it in ABAP Forum
ABAP Development
Regards
Suraj

Logical System Name of an Idoc Sender

Hi,
I have seen that For Idoc senders the the Logical System name associated with the sending Client has to be SAP+System Id(For example SAPE05 where System Id = E05).
Is it mandatory? If so how can I have multiple clients in a sender Idoc systems sending data?
Regards.

The logical system nameing convention is:
<System ID>CLNT<Client>.
If your system is ADM, client 070, the name would be:
ADMCLNT070.
Regards,
Jason

Same IDOC to two receiver system

I must send same IDOC to two receiver system..I am succeded to send an IDOC to abapProxy for only one system but i need to send it to two different system..I created two XI communication channels but i cannot create second receiver aggrement with same mapping.It gives an error "object already exists". But how can i assign this second communication channel without creating second receiver aggrement.
Our scenario like this
IDOC --> systemA abapProxy
--> systemB abapProxy
how can i overcome this situation?Could you explain step by step
Thanks

Hi,
in reciver determination, have SysA and SysB both as recivers by adding one more line in reciver section for SysB..........create a second interface determination with sender IDOC system and this SysB and create a XI comm channel for this SysB and create a reciver agreement for it also........
Regards,
Rajeev Gupta

PI system as IDOC receiver

Hi all
My scenario is send idoc's from SAP system to external adapter. This adapter can pick up the data from the logical system defined in we20 in SAP PI. then i will have to dowload the idoc in the logical system defined in SAP PI, . Is it possible to define the logical system in SAP PI and post the idoc's directly in SAP PI.
Can i use SAP PI as system as receiver IDoc system ? Did anyone faced these kind of scenario's ?
Any advice is highly appreciated
Thanks
Faizal

hi,
Interesting topic, 1st times that I hear that...
One of the legacy system has to SAP certified adapter , which has to capaablity to connect directly to SAP ERP system and download the IDoc's defined in the logical system LS.
What's the name of this commercial ECC adapter ? maybe you can contact the company who made it to know if this adapter is compatible with PI.
In my mind, this adapter had perhaps an interest when PI was not on the market to authorized a third-party to catch idoc (*), but with PI (since at least 7 years), I think your flow process has to be changed: PI should push Idoc to this third-party (so an easy flow "IDoc -> PI -> IDoc"), and not the opposite: the third-party which check inside PI... (which is I think not possible).
(*) without PI, in ECC, did your third-party pick-up an Idoc ? (so idoc status = 30 (wait)) or did it pick-up a file ? coz in ECC, as you know in WE20 you can decide how idoc is transfer: by an idoc port or by a XML-file or a HTTP...
I'm the feeling your previous flow is only like that: idoc (ECC) -> idoc (certified adapter for non-SAP third-party to receive idoc).
so maybe what you need is only to do: ECC (idoc) -> PI -> Idoc (adapter) to this third party... and then the third-party contine to use its certified adapter to be able to receive an idoc message.
regards.
Mickael
Edited by: Mickael Huchet on Dec 21, 2011 8:52 AM

Unable to convert the sender service ABC_Service to an ALE logical system

Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.

You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

EDI invoice idoc error "Enter a tax code in item 000001"

Hello,
I am trying ot post the EDI invoice but the idoc getting failed by giving error "Enter a tax code in item 000001".
Even i entered the tax code in my idoc, system not taking and also as i have maintained the table OBCD & OBCE but system not consider it.
If i maintained the tax code in my PO then it is posting the invoice with PO tax code sucessfully.
Please let me know, Is their any other setting needs tobe done for idoc to post the invoice without maintained TAX CODE in PO ?
Thanks in advance
Regards,
Satish

No option available .you have to maintain tax code in PO.
Try your luck with following option Still not sure as it works only if you call transaction MIRO
OLMR -- incoming invoice -- maintain default value for tax codes

How to send the PO IDOC error msg's to the concern users.

Dear Forum,
This is my requirement.
We are transferring sales order data from ECC 5.0 to ECC 6.0 through XI.And PO will be created in ECC 6.0 based on the sales order inputs.
When ever the SO data created in ECC 5.0.A sales Order IDOC will be generated and based on these details PO will be created in ECC6.0.Upto this level there is no problem and we have done this.
Source side : ORDRSP Idoc.
Target side : PORDRCP01 Idoc.
In addition to,If PO is not created in ECC 6.0.The suitable error msg will be reached to the concern user's mail ID's.
Please let me know to fulfill the pending task.
Thanks in anticipate.
Best Regards,
Naresh.K

Hi ,
Refer the Acknowledgments of Errors and Error Correction for Idocs.
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/frameset.htm
If the sender is not an IDoc system, you can use the Send ALEAUD
for Partner as Request function in the Integration Server to convert
acknowledgment IDocs to XI request messages and send them
or
Refer this link:
http://www.erpgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc
refer section of the doc 2.3.4. Set-up IDoc administration: (WE46)
Regards,
Sunil.

IDOC issue URGENT

Hi guys...
Sorry, I'm not sure where to post my IDOC questions...So I post it here and hope to get some opinion from u all...
Upon intercompany billing process is perform IDOC document should be generated to create posting in AP10. But now this is not the case, no IDOC generated upon this process...
When check the posting in AP10 and MY10 book and find out the value only posted in MY10 book but not AP10.
When I check the IDOC, system did not capture any error IDOC generated for the intercompany billing posting.
The message type for this IDOC that should be generated is INVOIC, which is the SAP standard IDOC.
Can anyone give me some suggestion on how to know what should be set in the system or it's the program problem? what makes the IDOC cant be generated for company code AP10?
Thanks.
Message was edited by:
KAR SENG LAW
Message was edited by:
KAR SENG LAW

Hi Sunil,
I didn't get your question. Can you be clear? Do you want to test the Idoc?
Thanks,
Vivek

SAP(Idoc) = XI = ThirdPart(WebService)

Hello friends!
I have a problem with development of acknowledgement system with SAP(Idoc) <=> XI <=> ThirdPart(WebService) scenario.
My case:
Scenario looks like:
SAP(Idoc) <=>(Idoc adapter) XI (SOAP adapter)<=> ThirdPart(WebService)
It must work this way:
SAP system send IDOC, then XI map it and send it via SOAP-adapter to third part webservice. Then webservice answer to XI with structure сontains "TRUE" or "FALSE",
and then XI must inform SAP ALE/IDOC system if current information from idoc was successfully added to webservice or not.
But how can I get it? As far as I understand ALE/IDOC system I have to create ALEAUD by myself, put status of idoc depends on webservice return and send ALEAUD idoc to SAP.
I'am right?

Hi,
You can use BPM for this Idoc--Soap Sync Process
Design objects:
Data type & Message Type
1) Import the IDOC and Later you import the Idoc, doble click on it a export it to your driver, next import it as External Definition for reason becouse if not, you wont be able to create a MI type synch with IDOC and genericResponse structure
2) Create data type for your Response Type of IDOC
3) Import the WSDL File For Request and the Response Type
4) Create the Message types according to the Data types which we created
Messgae Interface:
1) Outbound synchronous:
    output message will be ur idoc external definition file
    input message will be ur message type that u have created.
2) Abstract Outbound Synchronous:
    use the same as in Outbound Synchronous
3) Inbound Synchronous:
    input message will be ur request message of RFC/WebService
    output message will be ur response message of RFC/Webservice
4)Abstract Inbound Sunchronous:
    input message will be ur request message of RFC/WebService
    output message will be ur response message of RFC/Webservice
Mapping
Request Message Mapping:
b/w ur idoc external definiton and request message of RFC/WS
response Message Mapping:
b/w ur Response message of RFC/WS and ur message type
Interface Mapping
Import MI(abstract) of IDOC
Import MI of WS
select the mapping for request and response Tab
BPM
1) In container window define a variable named IDoc_ABS with category abstract interface and
    type (select the MI of IDOC alone)
   define a variable named GenericRespnse_abs with category abstract interface and type (select
   MI of genericResponse alone)
2) Create a Recieve Step --> in property message select the container you define before of idoc.
3) Define a Send Step--> mode synchronous
    select MI type abstract and sync (idoc and genericResponse)
    for property request message selects container Idoc_ABS
    for property response message selects container GenericRespnse_abs.
Save your Changes and thats all for BPM
*Configuration *
1) Create scenario
    Assign BS and create comunication channels with QoS (quality of service) type BE
2) Import your BPM
   Create a Receiver Determination
-->in the target service select the BPM. Save
-->In overview windown at foot windowns select MI IDoc_abs only. nothing else
Create a Receiver Determination
-->here the system who send data is BPM
-->in the target service select the BS of receiver system.Save
-->In overview windown at foot windowns select interface mapping and assing communication channel
what we do here. the flow is next
1) Receive data from sender system and send it to BPM
2) BPM call bs of target system (WS). how? because in interface determination you selected
   before the interface mapping
Regards
Seshagiri

Idoc- XI- Idoc - still awaiting acknowledgement

Hi guys!
We send Idoc->XI->Idoc and in sxi monitor we have a green flag - still awaiting acknowledgment. What does it mean? How can we be sure, that Idoc is received bu target application?
Thanx olian!

Hi Olian,
One way is to logon to R/3 system and use tcode WE02 or WE05 and there give your idoc type and press F8. you can see your idoc here.
Also go through it.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Note: IDoc technology supports its own acknowledgment technology, namely the ALE Audit. Here there are no acknowledgment requests from the sender. Instead, the receiver decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration. These acknowledgment IDocs are only used for monitoring on the sender side.
IDoc technology is the only technology in which positive acknowledgments from the application contain data. This data is sent by the IDoc adapter in an acknowledgment IDoc if the sender is an IDoc system. Otherwise, the data is discarded.
For the inbound IDoc adapter to be able to send an acknowledgment IDoc to the sender, a communication channel with the interface ALEAUD.ALEAUD01 must be maintained for the sender.
Regards,
Sarvesh
Message was edited by:
Sarvesh Singh

Status 56 in receiving system

Hi SDNers,
By BD87 transaction, I have to catch the status in receiving system.
To perform this task, I do the following steps:
1) Go to BD87 trx.
2) Select an idoc with status 3.
3) Execute the Tracing IDOCS system-wide (Trace IDOC).
I should obtain an idoc with status 53 in receiving system.
However, I finally obtain an idoc with status 56.
Where could I check to find the problem?
Thanks in advance for your help
Regards
Leo

Hi a®s,
Thanks for your soon asnwer. I've checked in the receiving system by WE20 and there is not an entry for my system source.
Are you talking about that when you say "idoc type is maintained"?
Thanks again
Regards
Leo

IDOC reduction gets always MATMAS05 as basic type

Dear Gurus,
I am trying to create a reduced IDOC derived from MATMAS message. I get always an associated basic IDOC type MATMAS05 but I would like this concrete reduction to be derived from MATMAS03.
Can somebody tell me what can I do so the system will reduce from MATMAS03 instead of MATMAS05 ?
I am using release 470 for the application ERP and basis has release 620.
Thanks

Hi ,
When you are reducing the Idoc, system will consider latest version of the Basic type of mesage type MATMAS,
You can not reduce previous version, this is SAP standard,
You have to reduce MATMAS05 based on u r requirement and create new Message,
Revert back if u have any queries...
Regards
Suresh.,D

XI vs Idocs system

Similar Messages

Maybe you are looking for