IDOC ALEAUD setup

Hi All,
Please let me know for IDOC ALEAUD setup between PI and ECC system
Thanks

ALEAUDIT
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
ALEAUD

Similar Messages

Idoc aleaudit ..question

Hi,
How does aleaudit work...i tried sending some idocs into sap r/3 and then ran report rbdstate for those message types...dint get anythign back..
then i tried to run the report manually and i keep getting msgs like "no data relevant to audit were selected " or "no parties are interested in the data"
Is there some config i am missing..Please dont point me to blogs/wiki`s for aleaud configuration..i have been through them..and also setup aleaud in the past..something is different in this scenario...
Venkat

Yes you are right..something is missing..what is the idoc basic type..you are sending..where are you running the rbdstate..on the r/3 system right ?
Regards
Ravi Raman

Error in IDOC(ALEAUD) to file Scenario

Hi ..
we have a client requirment were they want the ALEAUD acknowledgement in the form of file.
So we are creating a IDOC to file scenario, where IDOC is ALEAUD which is mapped to create a file in the traget system. but when we post the IDoc we get thwe following error.
*Note: have a small doubt. Can we use ALEAUD Idoc as a normal IDoc to File Scenario. because with the documents i understand that ALEAUD is a acknowledgment IDoc which is generated based on the request IDOC. but in our scenario we are manually using the structure of ALEAUD in the source system*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Kindly help me out .
Thanks in advance
Deepika

Hello,
If you need to send the ALEADUIT back to the SAP system if the file returns a successful ack, then you will need to have a BPM with a separate SEND step to send back the ALEAUDIT.
And check this ......
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
*******Reward points if found useful

IDOC Listener setup in SAP 4.6C

Hello,
from the documentation I've found the Idoc setup should be quite standard, but still real life is different. The 4.6C system here has no registered server program option in the SM59. When I try to test the connection I get the following error: program <PROGID> not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.
The operating system is HP-UX.
I would be glad to receive any hints.
Kind Regards,
Christoph Mertins

https://forums.sdn.sap.com/click.jspa?searchID=12426260&messageID=5211759 might help.
As this question is not directly related to MII would suggest you to search other forums as well.

IDOC Interface Setup using ALE

Hi,
Can any 1 suggest the best possible configuration steps to setup a idoc interface to two different systems

Hi Urstruly,
Please see the links below. They should help you reach your goal.
File to Multiple IDOC Splitting without BPM - Process Integration - SCN Wiki
SAP Library - SAP Exchange Infrastructure
Configuring Multiple Receivers in XI
Regards,
Jannus Botha

Acknowledgment through Idoc ALEAUD

Hi all,
I'm receiving an invoice from a third-party system in SAP ECC through the Idoc INVOIC01.
I have configured the Idoc ALEAUD01 to confirm to the 3rd-party system if the invoice has posted correctly. This Idoc sends out the idoc number of the inbound Idoc (INVOIC01) and the error text.
The Idoc number of the inbound Idoc (INVOIC01) was generated in SAP ECC, and the 3rd-party system does not know this Idoc number. So the 3rd-party system cannot match the confirmation with the corresponding invoice.
How can I do to include in the outbound Idoc (ALEAUD01) some data related to the received invoice?
I will appreciate any suggestion.
Regards,
Jaime S.

Standard programs for acknowledgments are not very flexible.
I suggest to copy standard program RBDSTATE into your custom Z* one. And make adjustments there. If necessary, you can also copy FM AUDIT_IDOC_CREATE.
Regards,
Dominik Modrzejewski

The iDoc ALEAUD.

Way does this iDoc come in to SAP R3 from XI ? And how can I prevent this iDoc beeing sendt from XI. I dont need it. It comes ever time I send an iDoc (DEBMAS, ORDERS etc) out of SAP R3.

Hi,
This is the acknowledgement for the IDOC processing of DEBMAS, ORDERS etc.
Use transaction SM36 to define a job using RBDSTATE and variant
SAP_AUDIT_SEND.
This is the background job schedueld, just stop this job.
refer below links to deactivate it
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Thanks
Swarup

Org modeler 4.1 IDoc Receiver Setup

Hi all,
in the "Deployment guide" for Org Modeler is indicated to use the following files:
sapjco.jar is version 2.1.10.
sapidocjco.jar is version 1.0 standalone.
sapidoc.jar version 1.0 standalone.
Unfortunatly, they aren't available in Sap Service Marketplace, that permits to dowload only sapjco3.jar and sapidoc3.jar
Where we can find the files?
many thanks,
Barbara

Hi all,
Sap answered:
=================
Please follow these steps in order to find the jco files you are lookin
for:
- Login to SMP
- Navigate to:
Products # Software Download # Support Packages and Patches # Search fo
Support Packages and Patches # Search Term: "jco"
- You will see the following results (see screenshot attached name "jco
files").
Nakisa Support
========================
Regards,
Barbara

IDoc Packaging + Ack ALEAUD = bad behavior ?

Hi,
I'm in version PI 7.11 and I'm studying the IDoc packaging of EhP1 with Acknowledgment (ALEAUD).
My scenario is a basic one: File -> PI --> ECC (100 idocs). And then ECC returns Ack.
So for the returned Acknowledgment, I have that:
- on ECC, I did ALE config, and I run programs RBDSTATE / RSEOUT00 to create one IDoc ALEAUD (Ack).
- In PI, I use a sender CC (Idoc adapter) by using option "Idoc Packaging".
- In PI, I use a Sender Agreement with Idoc ECC's ALEAUD and this sender CC.
- In PI, I use program IDX_ALEREQUEST on ECC's ALEAUD idoc.
My problem is:
ECC send me ONE idoc ALEAUD which contains 100 segments corresponding to 100 Idocs received at the first step. BUT even if I used the "Idoc Packaging"... in IDX5 of PI, I have not one idoc ALEAUD, but I have 100 Idocs ALEAUD !
And so after that my mapping is run 100 times instead of one ! Image if I need to return an email... with this PI behaviour, I will send 100 "Ack" emails.
So does somebody know why IDoc Packaging does not work with ALEAUD whereas program IDX_ALEREQUEST is correctly used ?
Thanks
Mickael
Note: I don't want to have to create a BPM to collect my ALEAUD Idocs. That's too heavy...
And (for the moment), I don't want to create a specific ZALEAUD idoc...

Hi Prashant,
yes, I did not precise it, but of course IDXNOALE is used, else PI will generate an Ack of this ECC's ALEAUD... so a ack of a ack... but it's not really my problem.
what I say is:
- Request : PI -> 100 idocs MATMAS (for instance)
- Ack : ECC return to PI only one idoc ALEAUD with 100 segments "E1STATE" corresponding to the 100 idocs MATMAS.
- Ack : PI receive this only one ALEAUD... but in IDX5 and in SXI_MONITOR, we see in fact 100 IDocs ALEAUD with 1 segment E1STATE, instead of having only one idoc ALEAUD (like in ECC side) !
So I'm searching a way to keep in PI the only one Idoc ALEAUD sent by ECC, in order to be able (for instance) to send only one email (and not 100 emails like it's the case for the moment).
Regards
Mickael

ALEAUDIT

What is ALEAUDIT with respect to IDOCs? when will they use it?

Hi
In short ALEAUDIT is nothing but the Acknowledgements for IDOCs
Using ALE audit you can monitor the processing status of dispatched IDocs in the receiving system (inbound) from the sending SAP system. The receiving SAP system periodically sends confirmation messages to the sending system. These confirmations are logged in IDoc status records and in separate audit tables in the sending system.
Ref: http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6550507d11d18ee90000e8366fc2/content.htm
Just have a look at this doc:
https://websmp207.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
Check this-
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/2a6550507d11d18ee90000e8366fc2/frameset.htm
TO configure
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
How to handle Ack for IDOC's
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
ALE audit is only possible for IDocs of type logical system (LS).
http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/content.htm
TO SETUP THE ALEAUDIT
Steps: if u want IDOC Ack You have to set up the ALEAUD.
Acknowledgment IDocs are always converted to XI acknowledgments.
This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.
Procedure
1. In the ABAP Editor (transaction SE38), under Program, enter IDX_ALEREQUEST and choose Execute.
2. Enter a sender port and a client and choose Execute.
3. Enter the partner number, partner type, and partner role for the receiver and choose Insert.
The entry is added to the table.
4. To delete an entry in the table, select the entry and choose Remove Entry.
Result
In the XI request message, the original sender of the acknowledgment IDoc is no longer known.
The XI request message created is a new message. Monitoring is not able to determine which was the original message.
File Acknowldgements
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Sending Acknowledgment IDocs as XI Request Messages
Use
Acknowledgment IDocs are always converted to XI acknowledgments.
This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.
Processing Acknowledgment Messages
An acknowledgment message informs the sender of an asynchronous message about the result of the processing of the message within SAP Exchange Infrastructure. The reported result is referred to as an asynchronous acknowledgment.
Request Messages
Within the request message you must define whether an acknowledgment message is required, and if so, what kind of acknowledgment message. The acknowledgment message can refer to two events:
● The arrival of the request message at the final receiver
● The execution of the application in the receiver system
For this purpose, the request message contains an acknowledgment tag, which specifies the event for which an acknowledgment is expected. This tag must be specified by the sender (or a sender adapter that supports acknowledgment messages).
Message processing in SAP Exchange Infrastructure ensures that the acknowledgment message follows the same route from the receiver to the sender as the request message did from the sender to the receiver. For this purpose, the request message contains a hop list that logs the route of the request message. This information is provided by all Integration Engines and Integration Servers that are involved in the processing of the request message.
Acknowledgment Message
As soon as the request message processing encounters an event that requires an acknowledgment, a corresponding acknowledgment message is created and sent to the sender.
An acknowledgment message receives a new message ID, but also has a reference to the message ID of the request message as well as the value Response in the Directory tag of the message header. The request message hop list is copied to the acknowledgment message header, thus enabling backward routing of the acknowledgment message.
If a message is branched, a separate acknowledgment message is returned for each newly created request message. These acknowledgments enable the sender to recognize that its original message has been branched.
Acknowledgment messages are processed using backward pipelines. These pipelines are defined for each pipeline involved in the processing of a request message:
Pipelines and Corresponding Backward Pipelines:
Pipeline
Backward Pipeline
SENDER
SENDER_BACK
CENTRAL
CENTRAL_BACK
RECEIVER
RECEIVER_BACK
The backward pipelines have the following main tasks:
● Transport from the receiver system to the Integration Server
The receiver system sends an acknowledgment message back to the corresponding Integration Server (RECEIVER_BACK), as defined for the local Integration Engine.
If a receiver adapter is involved in message processing, it sends the acknowledgment message back to the Integration Server, provided that the respective adapter supports this procedure. Otherwise, a final acknowledgment message is returned with a comment that an acknowledgment is not possible.
● Transport from the Integration Server to the sender system
The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
If a sender adapter is involved in processing the message, the Integration Server sends an acknowledgment message to the sender adapter, which is then responsible for returning the acknowledgment to the sender.
To do this, some adapter types require a corresponding receiver agreement for the sender.
Hope This Information is useful to you,
Thanks
Saiyog

PO to SO IDoc change (ORDCHG) - Extra condition pricing line generated. Why?

Hi guys,
My ECC6 system currently has an IDoc automation setup where creation/change of Purch Order will also trigger creation/change of Sales Order.
By default, condition pricing type will be PB00 or PBXX. I have implemented some code in EXIT_SAPLVEDB_001 to modify PBXX to ZP10.
This is done by modifying KSCHL in condition table DXKOMV in idoc segment E1EDP05.
What i want to achieve is when any current value is changed in the PO for PBXX, this new value should also reflect in ZP10 in the corresponding SO.
This is the problem i am currently facing:
1. First time change PBXX value in PO, ZP10 value in SO is changed correctly.
2. Second time changing the same PBXX line item value in the same PO, a brand new ZP10 line is generated in SO with the new value. The existing ZP10 line remains with old value and becomes inactive.
Is this normal behaviour? How do i ensure that a new ZP10 line does not get generated in the SO but is only being updated when there is an update in the PO?
Please help. Any input would be greatly appreciated.
Thanks in advance!

Hi Vioth,
Did you got solution for thsi i am also facing the same problem.If you konw the solution kindly suggest the solution for this
Thanks in Adavce,
Regards...............Kishore

Inbound IDoc not getting generated in XI System

Hi all,
I have created a scenario following the given weblog:
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
The first half of this scenario is working fine and the idoc data is getting posted into the the oracle table successfully.
The business process is successfully sending the acknowledgement IDOC 'ALEAUD' to the XI server using an HTTP Receiver Channel.
The problem is that no inbound IDOC can be seen in the XI system using tcode we05.
Next the xi system has to send the same IDoc to the R/3 system. But as no IDoc is getting generated in XI, nothing gets sent to R/3.
Can anyone suggest what could be the possible error.
Pls help.
Regards,
Neetu

Hi,
You will not see that IDOC in WE05 of the XI system. You can see that only in SXMB_MONI. XI system will not store any IDOC. When it enters XI it is a XML message and it will not post any IDOC that you can see in WE05.
If you need to send the IDOC back to R/3 system, you can use BPM and send back the IDOC to R/3. If you need few details from Oracle tables that is to be sent back to R/3 then get those values from Oracle tables and fill in the same IDOC and send it back to R/3.
Try this and let me know.
Thanks,
Prakash

IDocs in WEOUTQUEUE not processed

Hi all,
I have a problem with IDocs' serialization. I want to send IDocs of specific message types via IDoc outbound queue (trans. WEOUTQUEUE) .At sender system side in outbound partner profile (WE20) I configured IDoc to be send by Queue Processing with rule "constant:ediqueue". IDocs arrive to queue in WEOUTQUEUE, and here the problems begin:
1. Processed messages stay in queue - why?
2. If I send 1 IDoc it's not sended automatically, I have to activate queue in order to process it. It ried to use report RSEOUT00,but it only shows how many IDocs ready for processing and doesn't send them - how can I configure automatic processing of Idocs in queue?
3. If I send (with WE19) more then 1 IDoc at once, thay are automatically processed, but in XI in SXMB_MONI i see that they are processed by random QRFCs and are not serialized.
Can anyone please help me to work it out?
Thanks!
Anna.

We are having a similair issue. I have IDocs outbound from R/3 to XI. The Idocs are setup as "Queue Processing" with "Transfer IDoc Immed" option in the WE20 partner profile for EOIO processing. I usually have no problem all day long but every night right after midnight all the Idocs remain in a status 30. I have to use WEOUTQUEUE to activate the que or BD87 to release them. Once I do this, all IDocs moved along successfuly except every once in awhile during the middle of the day they go into a status 30 and remain there. I did notice the difference between the Idocs that work and the others that get stuck is the there are 2 entries for status 30 when viewing the IDocs in WE02. Here is what they look like. IS this simialiar to your issue?
03 - qRFC used to send IDoc to SAP system (I get this once I releaqse them manualy)
30 - blank
30 - Receiver exists , No filters , No conversion , No version change
01 - blank

IDOC extraction in file format in a customized manner

Hi Experts,
I have an IDOC : pexr2002 (payment instructions). In this IDOC bank id field is there.
My requirement is:
I need to create a transaction with 'Save' button
By clicking on 'save' button, the idoc should be triggered and if the bank id field is equals to 'scb', then IDOC should be downloaded into local folder
how can I do this.
Edited by: kalandar on Mar 18, 2010 8:49 AM
Edited by: kalandar on Mar 18, 2010 10:09 AM

Hi,
If you are lokinf for IDOC acknowledgements means check these
setting up Audit Response.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
ALEAUD need at least following fields to be filled:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
If you are using XI 3.0 SP12 then there is some bug See : 828277
Just have a look into this blog-/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Or else if you are looking to receive the File Acknowledgements means have a look at this
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards
Seshagiri

BPM Receive IDOC Acknowledgment

Hi there,
my scenario: JDBC -> XI -> IDOC -> ALEAUD -> XI -> JDBC
Is it possible to receive async IDocAcknowledgment and update all rows of the first (sync) receive step via (sync) jdbc ?
It's a typical masterdata scenrio which selects via jdbc some data from the legacy system and creates idocs for r/3.
thanks and regards
Sebastian

This should work when you open a S/A Bridge on your receive step.

IDOC ALEAUD setup

Similar Messages

Maybe you are looking for