IDOC Acknowledgement and Header Mapping

Dear all,
I've got the following scenario:
SAP 4.6C is sending many different IDOCs to XI 3.0 (SP14).
On XI side there are several integration processes, business systems and business services receiving the IDOCs.
I want to create IDOC acknowledgements and send them back to SAP system.
For one integration process I was able to successfully create and send back an acknowledgement by following the steps described in the very good blog:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Now I want that every integration process/business system/business service is sending back an acknowledgement with the same logical system name (meaning "this acknowledgement is coming from XI").
As it is not possible to enter the same logical system name for more than one process I created a receiver agreement with:
Sender Service = the integration process
Receiver Service = the SAP 4.6C business system
Receiver Interface = ALEAUD.ALEAUD01
Receiver Communication Channel = IDOC receiver channel called "Ack_IDOC_Receiver", existing in SAP 4.6C business system and pointing to this system
Additionally I created a header mapping in this receiver agreement where I set the Sender Service to the business system of the XI system.
Unfortunately the tests showed to me that obviously the header mapping (maybe even the whole receiver agreement) is being ignored completely as no Acknowledgement IDOC will be created. Instead I get the error message "Unable to convert sender service to an ALE logical system".
I also played around a bit with the options "Apply Control Record Values from Payload" and "Pass Sender value from Payload" but this didn't make any difference.
Why is the header mapping not replacing the sender service in the acknowledgement message?
Best regards,
Tobias

Tobias,
we have the same Problem.
we´re sending with Receiving Partner "12345" and the IDoc in the target System is filled with the standard SAP Value maybe the one configured in the SDL.
We have configured our IDOC_REceiver with a mark on "Apply Control Record Value from payload".
If you have a look at the SAP Helpfile you will find out that some header fields are not be changeable and get the value from sap.
like IDOC-Number, Receiving Partner and maybe the sender service ???
Regards,
Gordon

Similar Messages

Idoc Acknowledgements and Idoc Packaging

All,
I am implementing a requirement wherein we need to post 2 different types of Idoc's from our BPM. The Business requirements is such that until the Idoc 1 is not processed by the R3 system, the Idoc 2 should not be posted from XI as there is dependency in the data.
This can be addressed using Application Acknowledgements. The solution to this is to use the send step in my BPM with application acknowlegement. Until the application acknowledgement is not received for the first send step , the next send step will not be processed and so things will / should work fine.
The problem comes in the fact that the Idoc's being sent out of XI use Idoc Packaging, ie., the First Send Step uses Idoc Packaging to post multiple Idoc's to the target system. A question that arises due to Idoc packaging and Idoc ack's are,
How will the Idoc Ack's be sent back to XI?
I have read through the online help and it states that every ALE AUDIT Idoc can contain the status of maximum 500 Idoc's. Now, in my case , when using my Idoc packaging, if the number of Idoc's are greater than 500, how will the Application Acknowledgement for the Idoc's work? Will I still get a single acknowlegement in my BPM or will I get multiple acknowledgements? Will Send Step with Application acknowledgement still hold good?
Any ideas, thoughts / experiences on using idoc ack's with idoc packaging?
Regards
Bhavesh

If I undestatood correcty you have 2 send step, the first send a message containing multiple IDoc (IDoc Packaging). In this first send step you set the application Acknowledgements.
I think that this is not managed from the BPM, bacause the acknowledgements will come someone positive and someone negative, and so when the first send step will be completed ?
I think that the solution must to be changed a little bit, or removing the IDoc Packaging, or removing the wait of Acknowledgements.
Also take in mind that if you use a BPM with many possible correlation (Acknowledgements) you will have bed performances.
Regards,
Sandro

Idoc Acknowledgements and BPM.

All,
My current requirement is to post an Idoc from my BPM, and get back the Idoc Acknowledgement. On the basis of the status field in the ALEAUDIT Idoc I need to determine the further course in my BPM.
Option 1:
1. In the Send Step of my BPM , I can request for Application Acknowledgement. I have done this and am able to receive the Acknowledgement and see the same against the Acknowledgement Msg ID in MONI. I am able to see the ALEAUDIT idoc triggered for my Send Step back to my BPM .
The question in case we are to use this Option is , how do I access this AleAudit Idoc message in my BPM. As I want to have a switch, I need this to be populated in a container element of my BPM. Is this possible? Is this approach a correct one? Any Ideas?
Option 2
I can have a Send Step in my BPM to send the Idoc from XI to R3. this will be a normal Send Step with no Acknowledgements. I can also use a Receive Step in the BPM to receive the ALEAUDIT Idoc back to the BPM.
This I guess can be done with a Receive determination where R3 is the sender and the AleAudit Idoc is the receive etc.
Issues with this approach, I need to use a Correlation against the Send and Receive Step to send the Idoc and receive the AleAudit.
1. What is the Correaltion that can be used? Is there a standard correaltion. for such cases?I looked into the Idoc and the AleAudit but could' nt find a suitable Correlation Field.
Do both these solutuons make sense? has anyone got a better approach?
Any comments are appreciated.
Regards
Bhavesh
PS: Have gone through the How to guide on Idoc Ack's and the blogs on SDN as well. But if still someone feels that there is a blog that is relevant to this issue, please do let me know if I have missed anything.

Ha, now that was interesting question. Brains were rusty, relooked into that lookup and these are the fields of the IDXRRCVPOR we use,
Used the RFC - RFC read table
XI's Idoc Number is in Field IDOCNUMBER
Original SAP IDoc Number is in Field SNDLAD.
Code excerpt attached below.
@ Henrique : Work's been crazy past few months. The blog is on my to do list, hopefully someday soon it should be out. My Apologies guys!
Channel rfcChannel = LookupService.getChannel(BusinessService, CommChannel);
//As the call is being made to RFC, RFCAccessor is obtained.
rfcAccessor = LookupService.getSystemAccessor(rfcChannel);
rfcXML =
 "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:RFC_READ_TABLE xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><DELIMITER/><NO_DATA/><QUERY_TABLE>IDXRCVPOR</QUERY_TABLE><ROWCOUNT/><ROWSKIPS/><DATA><item><WA/></item></DATA><FIELDS><item><FIELDNAME>SNDLAD</FIELDNAME><OFFSET/><LENGTH/><TYPE/><FIELDTEXT/></item></FIELDS><OPTIONS><item><TEXT>IDOCNUMBER EQ '"
 + SourceDocNum
 + "'</TEXT></item></OPTIONS></ns0:RFC_READ_TABLE>";
inputStream = new ByteArrayInputStream(rfcXML.getBytes());
XmlPayload inPayload = LookupService.getXmlPayload(inputStream);
Payload outPayload = rfcAccessor.call(inPayload);
responseStream = outPayload.getContent();
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
/* Create DOM structure from input XML */
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(responseStream);
NodeList list = document.getElementsByTagName("WA");
for (int k = 0; k < list.getLength(); k++) {
 Node node = list.item(k);
 if (node != null) {
 node = node.getFirstChild();
 if (node != null) {
 if (!node.getNodeValue().equals("")) {
 OutputDocNum = node.getNodeValue();
Regards
Bhavesh

Reg:HEADER MAPPING

I really want to know the use of HEADER MAPPING IN IDOC based scenarios : for what purpose do we need to specify the fields
sender service:
sender party:
receiver service:
receiver party:
in header mapping,if header mapping is not specified do IDOC based scenarios works?

HI,
You need not specify the header mapping in IDOC based scenarios. If its idoc to file then you have maintain adpater specific identifiers in your business system. If its file to idoc then too header mapping is not necessary.
Follow these links.
https://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC-Part2+%28Configuration%29
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC-Part3%28StepsrequiredinXIandR3%29
https://wiki.sdn.sap.com/wiki/display/XI/StepbyStepProcedureofIDOCtoFileScenariousingBPM
Regards,
Merrilly

Idoc Acknowledgement in File

Hi All,
I came through some threads in SDN regarding Idoc acknowledgement and followed handling Idoc acknowledgement document. I am able to get back acknowledgement(ALEAUD) in Xi.
I configured a scenario to receive this acknowledgement in File.
But i am not able get the acknowledgement in the File.
In SXMB_MONI ,in the pipeleine step Technical Routing of Response i am getting Acknowledgement Message Stopped.
How to rectify the above error..I need to get the acknowledgement back in File..?
Is it possible to do without BPM..?
Hoping for good solution..
Thank You
Regards
Prakash

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

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

>so i cant use apply control rec values from payload.........
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

Automatic Payment Process through IDOC and Receive Message Acknowledgement and BANST file format

Hi Experts,
We are implementing payment process to our client through Idoc.
Normally the process will go like below. Once Payment Initiated --> IDoc will generate --> This Idoc process through PI system and send to Bank.--> Once payment data received bank --> it will generate acknowledgement receipt and Bansta file and send it PI system --> This PI system system again send it --> SAP system. Here I want to know the required configuration from PI system to SAP system while receiving acknowledgement and Bansta file. And let me know if u guys have steps...
Thanks,
Raviram

Hi,
>is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
yes
>In that case what should the Message Type we are using in the file-sender adapter look like?
If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
Regards,
Udo

Multiple Message Mapping with same Idoc, Sender and Receiver

Hi,
We have one Interface sending INVOIC02 Idoc from SAP R3 4.6C to SAP R3 4.6C through XI 3.0.
On Inbound side we are using SAP standard configuring one Partner Profile with inbound INVOIC MM process code INVL.
In customizing, we have defined one invoic type for the EDI partner.
Now we have to integrate another type of inbound invoic, but in customizing it's not possible to assign more than one invoic type to the same Partner EDI.
So, we have a restriction in SAP 4.6C inbound standard. On the other hand, we can't desing two Integration Scenarios in XI 3.0 with the same idoc INVOIC02, for the same sender service and receiver service because Integration Directory doesn't allow to create two interface determination for them.
We are thinking on using header mapping in XI (receiver agreement to avoid use the same EDI partner profile for the inbound invoic, but we can't assign the same client and technical system with the same ALE Logical System in SLD for two different business systems.
Does anybody have any solution for this problem, SAP side or XI side?.
Thank you
Best regards
Luis

Hi!
In XI configuration - interface determination, you can specify more than one Inbound interface. If you identify more than one, you get a new column where you specify condition (xpath) for selecting between the different inbound interfaces.
In 4.6c, you can have more than one inbound invoic for the same EDI partner profile, if you separate between them using message function. Just add a new inbound parameter with a different message function, or copy the one you have and specify another message function, i,e. "DIFF".
Hope this helps.
Regards,
Oeystein

Sending IDoc Batches to SAP: Issue with Header Mapping for SNDPRN

We are sending batched IDocs from XI to SAP. We need the individual IDocs to reflect different SNDPRN values. Our mapping creates the different IDoc EDI_DC40 record correctly with different SNDPRN values. However, XI wipes out the SNDPRN values in the payload. When we define Header mapping to get the Sender Party as the XPath to the SNDPRN in the payload, then the header mapping errors out because the XPath returns multiple values.
I wanted to know if anyone has successfully implemented sending IDoc batches to SAP from XI with different SNDPRN values.
Your feedback is appreciated.
Jay Malla
Licensed To Code
Genentech SAP XI Team

Hello,
I have the same problem. I want XI send an IDOC with the SNDPOR, SNDPRT and the SNDPRN that are in the EDIDC40.
I find this in sap.help : 
Mapping
The IDoc adapter does not make any special demands on mapping. The IDoc adapter must simply be provided with an IDoc XML structure at the Integration Server outbound channel. This either already exists or must be generated by using a mapping.
If the IDoc XML structure contains a control record, it is deleted and created again by the IDoc adapter. If you want to include additional values in the control record, you must select the Apply Control Record Values from Payload checkbox in the parameters in the communication channel and provide a corresponding mapping for the values.
You can include the values from the following fields in your IDoc control record:
MESCOD, MESFCT
TEST
EXPRESS
STD, STDVRS, STDMES
SNDSAD, SNDLAD
RCVSAD, RCVLAD
REFINT, REFGRP, REFMES
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
Perhaps we must use party configuration but I don't know how do this !
Regards,
Chris

IDoc storage and mapping in PI

As part of our Middlware Migration from Websphere to Datastage , I am being told by my Datastage team that in SAP ECC, I would have to define an Unique IDoc type for every Interface. This is to facilitate for the Datastage to extract just the IDocs relevant for a given Interface/Partner at a given time instead of scanning through all the IDoc types and then filtering on Message type and any other attributes necessary to map and push the Idoc/file to a partner . ( Apparently there is a file folder based on IDoc type in Datastage, for example all ORDERS05 Idocs go into one folder, ZORDERS5 go into another folder) .
My question is that does PI have any functionality where it stores IDoc data based on not just IDoc type but any more freely definable IDoc control attributes like for example Message Type? So that there could be separate files/folders for every IDoc type/Message Type combination?

1. Scenario IDoc Sender --> SOAP Receiver with XSD validaton on integration server
Is a negative system acknowledgement also sent back via ALEAUD if there is a processing error in PI, such as XSD validation failed, message mapping error etc. So all errors that occur before the message is sent out?
its only a transport acknowledgement like idoc has been received in PI..but there is no option to send any errors or mapping errors messages back to sender system.
2. Scenario Proxy Sender - BPM - AS2 Receiver
If I request technical acknowledgements in an integration process send step. Is it then possible to handle a negative acknowledgment if an error in the send step occurs? So, to create a message and send it back to the sender system?
No there is no option like that....
HTH
Rajesh

Header mapping while using IDoc as receiver communication

Hi All,
Can any one brief me with header mapping while configuring receiver determination when IDoc is used for receiver communication.
Thanks,
Govindu.

Hi,
To change the Partner Type( SNDPRT and RCVPRT ), you use Header mapping in the receiver agreement.
If you use APPLY CONTROL RECORD FROM PAYLOAD, the following values are filled from tha payload,
MESCOD
MESCFT
TEST
EXPRSS
STD
STDVRS
STDMES
SNDSAD
SNDLAD
RCVSAD
RCVLAD
REFINT
REFGRP
REFMES
STATUS
DIRECT
OUTMOD
CREDAT
CRETIM
Take sender from payload and take receiver from payload, are used to change the value of SNPRN and RCVPRN.
Regards,
Bhavesh

Mapping every row to an idoc with same header

hi,
i have record:
recordset 1..1
Header 1..1
Row 0..unbounded
i want to map it to :
idoc 0...unbounded
Header 1..1
Row 1..1
i want every row in source will create an idoc. every idoc will have same header but different row.
can u please explain how do i do that?
thanks,
Tomer

Hi,
Map row node with IDOC node. It will create an IDOC per row.
Now map header node with header node. Between the header nodes you have to create a User defined function commonlly named CopyPerValue:
public Void copyPerValue (String[] a, String []b, ResultList result, Container container){
for (int i=0; i<a.length; i++){
 result.addValue(b[0]);
You have to map row with a. And header with b.
Regards,
Carlos

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Issue with IDOC occurence and SeeBurger message mapping

Hey Guys
While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
I just want to make sure before i start off with doing whole of the mapping manually.
Thanx
Aamir

Thanx for the input guys
@Deepthi.
Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
>>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
@Jens
>>The XI message mappings from Seeburger in the Industry solutions are mapping templates
Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
@Seshagiri
>>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
Looks like i need to do it manually
Thanx
Aamir

Header and mass mapping

Hi guys
What is the use of header mapping ? What is the use of mass mapping ?

HI
Header mapping mainly used in B2B scenario
Refer to my answer in this thread
Re: Header Mapping
I dont think there is a concept of mass mapping in XI/PI but portal do have mass mappings.
If you refer to Message mapping then it is required to map the payload of the source and target messages
Thanks
Gaurav

IDOC Acknowledgement and Header Mapping

Similar Messages

Maybe you are looking for