on 03-15-2008 11:21 PM
Hi,
We are hving a scenario as below, NOTE : We have the pdf.." how to idoc acknowledgments" AND Still Stuck
Confirmation aleaud
Sys A <--
*Sys C*
EDI Partner -
> XI -
> R/3
EDI IDOC(orders)
We need to send an acknoelledgment of the idoc posted in R/3 back to the EDI system..
I read the document "How to idoc ack"
We have set up the distribution model, with filters for only aleaud, Basis also did the ports/partner profile config ON SYSTEM C
We have run into a strange issue while trying to schedule the background job RBDState...!!!!!!!!!, We get a pop up.." No parties are interested in the data" or "No audit data found"..when we can see 100`s of Idoc`s..., We were told the parameters used to schedule the back ground job arent right...
This is my question Gurus...
As per the diagram above can someone help us correctly fill the params below, these need to be done in the System C as above..right..Please correct me..if wrong
1) Confirmation to System -
> ______________ to ____________________
2) Message Type -
> _____________ to _______________________
3) Message Code --> _______________ to ________________
4) Message Function ---> ______________ to ______________________
5) Data Idoc Changed ---> _____________to ___________________
Last but not the least...is there anything else we need to do So that when we post an idoc we get an aleaud..from the R/3 system...
Can someone who has done this please help..........
asas
Hi,
If it comes to parameters of RBDSTATE report I would provide only:
Confirmation to System: <your logical system name for which you have configured inbound partner profile>
Message Type: ORDERS
When ORDERS reaches the target systems, are ALEAUDs being generated? -> bd87
Make sure that distribution model is configured for appropriate logical systems too.
If you are receiving ALEAUDs in XI (idx5), have you configured properly receiver IDoc adapter?
Make sure that you do not suppress acknowledgments for your message type.
Regards,
Jakub
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check the
IDXNOALE table: and see if the port, the
client of the sender, and the message type id there
The flow would be,when Idoc reaches receiver R/3 system, Ack would come to XI after executing report RBDSTATE on R/3
More details on how to switch off ALE audit messages are available in SAP Note Number : 777175.
ALEAUD need at least following fields to be filled:
MESTYP: original message type
DOCNUM: original IDoc number
STATUS: 68 in case of error, 53 in case of success
STATXT: Short description for R/3 user what has happend
Refer
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks
swarup
Swarup,
I am looking for parameters for RBDSTATE..not how to turn off idoc ack...etc...and what params need to be filled in aleaud..
For aleaud to be generated we need to run RBDSTATE ....on the recieving system...i was looking for the specific params that need to be filled in..as i was getting weird
msgs like
" no audit data generated "
" no one is interested in the audit data.."
asas
Hi,
Please check this
setting up Audit Response.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
For IDOC, you could have ALEAUD as an acknowledgment IDOC.
Check this document on handling IDOC acknowledgements. This might give you some pointers.
have a look at the Alert Framework, which can be configured to send mails to specific persons if an interface processing fails.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
There are two types of JDBC acknowledgements Transport level and application level.
IF the JDBC call is asynchronous you can set up for transport level acknowlegement in the send step in ur BPM.
if the JDBC call is synchronous then JDBC adaptor will generate a response message with a tag update count, which gives you the number of rows that were updated.
refer to the following link, which details about reciever jdbc
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
just check out these links
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
Thanks,
Bhargav.
Note:Award points if found useful
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.