Context handling in message mapping for an IDoc to File Scenario

Hi,
Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
Header (1..1)
Detail (0..Unbounded)
         DependentDetail (0...Unbounded)              Note: This dependentdetail is a subelement of Detail
Trailer(1...1)
I created my target structrure the same way as the Idoc structure.
My output is a simple text file. I need the output in this format
Header
Detail1
   Dependentdetail1
   DependentDetail2
   DependentDetail3
Detail2
   DependentDetail1
   Dependentdetail2
Detail3
Detail4
Trailer
Since the Detail and Dependent Detail records are unbounded .
But right now i m getting my output like this:
Header
Detail1
Detail2
Detail3
Detail4
Trailer
But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
Thanks,
Adam
Edited by: hymanroth on Apr 29, 2011 11:11 PM

Thanks Kenneth foryour quick reply,
Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
my content conversion is as follows:
Header.fieldNames
Header.fieldFixedLengths
Header.endSeparator
Detail.fieldNames
Detail.fieldFixedLengths
Detail.endSeparator
DependentDetail.fieldNames
DependentDetail.fieldFixedLengths
DependentDetail.endSeparator
Trailer.fieldNames
Trailer.fieldFixedLengths
Trailer.endSeparator
So As I told earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
Thanks,
Harsh
Edited by: hymanroth on May 2, 2011 7:03 PM

Similar Messages

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

Context handling during message mapping

Hi,
I'm working on a mapping and it almost works. There is just 1 thing to solve. I use the fixvalues funtion with as input a field A in a segment of my Idoc. This function is used to map a field B in another segment. However as this segment has multiple occurences, I have problems with the context handling: the first timle works ok but then it fails (as the filed A is in another segment/context). How could I fix this? I would like to avoid UDF as I don't know much java.
Kind regards,
Ulrich

Hi Ulrich,
Mapping A_source-Fixvalue-B_target
In the above case What are the elements exist in A_Source same thing will be transfered to B_target . If it is not find any value in Fixvalue table then it will pass the default value. So provde the default value.
If there is not element in context then it won't create b_target not at all for that context. So use the Mapwithdefault() nodefunction before passing the value B_target. so in that case it will generate the empty value instead of none.
Warm Regards,
Vijay

Message mapping issue in idoc to jdbc scenario

We have a scenario of idoc->XI-JDBC
the below given segment may get repeated , as shown below ,
E1EDP19[2]--idoc segment
   QUALF---003
   IDTNR---01000123(Bar Code No)
E1EDP19[3]--idoc segment
   QUALF---003
   IDTNR---20500000000034(EAN No)
Reqd mapping
if QUALF=003
THEN IDTNR----->Bar_code_Number_EAN
Now IDTNR has to be mapped with Bar_code_Number_EAN for the segment which comes last
Pl suggest how to map using graphical mapping for the above scenario.

Hi Raj ,
The current mapping works fine if the parent segment E1EDP01 is only one but if that gets repeated then the last value of IDTNR is getting populated in the target side, very clearly i m giving the source and target structure and the mapping done using the UDF
Source structure
E1EDP01
       E1EDP19[1]--idoc segment
              QUALF---002
              IDTNR---01000123(Bar Code No)
       E1EDP19[2]--idoc segment
              QUALF---003
              IDTNR---01000123(Bar Code No)
       E1EDP19[3]--idoc segment
           QUALF---003
           IDTNR---20500000000030(EAN No)
E1EDP01
     E1EDP19[1]--idoc segment
                QUALF---002
                IDTNR---01000123(Bar Code No)
     E1EDP19[2]--idoc segment
               QUALF---003
               IDTNR---01000123(Bar Code No)
      E1EDP19[3]--idoc segment
             QUALF---003
             IDTNR---20500000000031(EAN No)
E1EDP01
       E1EDP19[1]--idoc segment
               QUALF---002
                IDTNR---01000123(Bar Code No)
      E1EDP19[2]--idoc segment
              QUALF---003
              IDTNR---01000123(Bar Code No)
     E1EDP19[3]--idoc segment
          QUALF---003
          IDTNR---20500000000032(EAN No)
Target mapping
if QUALF=002
THEN IDTNR--->Article_No this is the direct mapping so , no issues
if QUALF=003
THEN IDTNR----->Bar_code_Number_EAN, now this IDTNR should get repeated every time the segment E1EDP01 gets repeated , currently only the last value form all the IDTNR is coming to the target side.
The current mapping works fine if the parent segment E1EDP01 is only one
Target structure
Access1
IDTNR--> Bar_code_Number_EAN( value is 20500000000030)
Access2
IDTNR--> Bar_code_Number_EAN( value is 20500000000031)
Access3
IDTNR--> Bar_code_Number_EAN( value is 20500000000032)
Current mapping
If QUALF = 003
                Then QUALF ---->
                                                 mapBarCodeEAN---->Bar_code_Num_EAN
If QUALF = 003
                Then IDTNR ---->
Context of QUALF is set to E1EDP01
Context of IDTNR is set to E1EDP01
thanks for your personalised help
rgds
mojib
Edited by: mohammad mojib ur rahman on Apr 9, 2010 1:30 PM

Message mapping challenge in IDOC to EDI scenario

Dear PI message mapping experts,
I'm a newbie in PI and facing a mapping problem using graphical message mapping.
I'm in an IDOC (INVOIC.INVOICE02) to FILE (EDI) scenario.
Here after is the mapping i need to perform :
Source structure IDOC :
<E1EDKA1> (0..99)
 <NAME1> A </NAME1> (0..1)
 <NAME2> B </NAME2> (0..1)
 <NAME3> C </NAME3> (0..1)
 <NAME4> D </NAME4> (0..1)
</E1EDKA1>
Target structure :
<AccountingCustomerParty> (1..1)
 <Party> (0..1)
 <PartyName> (0..unbounded)
 <Name>A</Name> (1..1)
 </PartyName>
 <PartyName>
 <Name>B</Name>
 </PartyName>
 <PartyName>
 <Name>C</Name>
 </PartyName>
 <PartyName>
 <Name>D</Name>
 </PartyName>
 </Party>
</AccountingCustomerParty>
I know i have to play with context and queues with stanard function or UDF but cannot succeed to do it.
Could you please help me ?
Thanks in advance,
Alysee

One approach out of available few ways to implement this:
NAME1 - Exists - CreateIf - PartyName[0]
NAME2 - Exists - CreateIf - PartyName[1] (Create deuplicate segment)
NAME3 - Exists - CreateIf - PartyName[2] (Create deuplicate segment)
NAME4 - Exists - CreateIf - PartyName[3] (Create deuplicate segment)
Srikanth Srinivasan

Mapping Error- In IDoc to File scenario

Hi Experts,
Got the Mapping error for one interface (IDoc to file). After comparing with successful message found that the field value (TDLINE) is not availbale in first segment (E1EDT10) in idoc for this failed one.
Mapping is :
TDLINE -- Exists --- Creatif --- Receiver field(in the file)
But here due to the the empty value in first segment the message is failed in XI system, next segment values is not trasmitted to the recever end(maping is the same above). To overcome this issue please suggest the suitable mapping design in IR.
Regards
Mahesh

Hi,
After your CreateIf, use a "IfWithoutElse" by selecting the properties "Keep SUPPRESS Values". To do that, do a right click on IfWithoutElse, choose "Properties".
With this option, you will keep the fact that you have nothing in the source, and so the target context will have a "SUPPRESS" line. I have not THE solution, so do your own test.
If it's not enough, see also about the "mapWithDefault" (but that depends of your real rule).
Regards.
Mickael

Questions to a Mapping for IDOC-to-File Scenario

Hi all,
I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
<xdoc>
 <Invoice>
 @purno
 <HeaderInfo>
 <invno/>
 <shipdate/>
 <extvalue/>
 </HeaderInfo>
 <DetailInfo>
 <LineItem>
 @lineno
 <vpartno/>
 <descrip/>
 <qtyord/>
 <cost/>
 <vendmemo/>
 </LineItem>
 </DetailInfo>
 </Invoice>
</xdoc>
The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
Is it possible to implement this process with a common message-mapping or have I to implement a business process?
Thanks
with best regards
Christopher

Hi Christopher,
Is it possible to implement this process with a common message-mapping or have I to implement a business process? - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
Thanks,
Rajeev Gupta

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier classifier
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
classifier attID classifierAtt
classifier destSourceMsg MainDocument
classifier showInAuditLog true
bic classifierAttID classifierAtt
bic destEncoding UTF8
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName AUTO
bic newLine true
bic srcEncoding UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
 <D_I01>00</D_I01>
 <D_I02/>
 <D_I03>00</D_I03>
 <D_I04/>
 <D_I05>ZZ</D_I05>
 <D_I06>CELORGS01</D_I06>
 <D_I05_2>ZZ</D_I05_2>
 <D_I07>AVX</D_I07>
 <D_I08>032008</D_I08>
 <D_I09>1718</D_I09>
 <D_I10>X</D_I10>
 <D_I11>00401</D_I11>
 <D_I12>000000008</D_I12>
 <D_I13>0</D_I13>
 <D_I14>T</D_I14>
 <D_I15>^</D_I15>
 <S_GS>
 <D_479>PO</D_479>
 <D_142>CLS01</D_142>
 <D_124>058895921</D_124>
 <D_373>20080320</D_373>
 <D_337>1718</D_337>
 <D_28>8</D_28>
 <D_455>X</D_455>
 <D_480>004010</D_480>
 <S_ST>
 <D_143>850</D_143>
 <D_329>800001</D_329>
 <S_BEG>
 <D_353>00</D_353>
 <D_92>SA</D_92>
 <D_324>4500005037</D_324>
 <D_373>20051110</D_373>
 </S_BEG>
 <S_CUR>
 <D_98>BY</D_98>
 <D_100>USD</D_100>
 </S_CUR>
 <S_FOB>
 <D_146>CC</D_146>
 <D_309>OR</D_309>
 <D_352>FREE CARRIER</D_352>
 <D_334>02</D_334>
 <D_335>FOB</D_335>
 <D_309_2>DE</D_309_2>
 </S_FOB>
 <S_ITD>
 <D_336>01</D_336>
 <D_333>3</D_333>
 <D_351>45</D_351>
 </S_ITD>
 <G_SN9>
 <S_N9>
 <D_128>L1</D_128>
 <D_369>GEN</D_369>
 <S_MSG>
 <D_933>TEST</D_933>
 </S_MSG>
 <S_MSG>
 <D_933>MESSAGE</D_933>
 </S_MSG>
 </S_N9>
 </G_SN9>
 <G_SN1>
 <S_N1>
 <D_98>BY</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 <S_PER>
 <D_366>BD</D_366>
 <D_93>Graham Crawford</D_93>
 </S_PER>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>BT</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>SE</D_98>
 <D_93>3M COMPANY</D_93>
 <D_66>92</D_66>
 <D_67>0000019591</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>ST</D_98>
 <D_93>SAMPLE</D_93>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SPO1>
 <S_PO1>
 <D_350>00010</D_350>
 <D_330>10.000</D_330>
 <D_355>EA</D_355>
 <D_212>10</D_212>
 <D_639>PE</D_639>
 <D_235>BP</D_235>
 <D_234>230-1812-01JDS</D_234>
 <D_235_2>EC</D_235_2>
 <D_234_2>A00000000000002</D_234_2>
 <G_SPID>
 <S_PID>
 <D_349>F</D_349>
 <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
 </S_PID>
 </G_SPID>
 <S_REF>
 <D_128>CO</D_128>
 <D_127>4500005037-00010</D_127>
 </S_REF>
 <G_SSCH>
 <S_SCH>
 <D_380>10.000</D_380>
 <D_355>EA</D_355>
 <D_374>002</D_374>
 <D_373>20051208</D_373>
 </S_SCH>
 </G_SSCH>
 </S_PO1>
 </G_SPO1>
 <G_SCTT>
 <S_CTT>
 <D_354>1</D_354>
 </S_CTT>
 </G_SCTT>
 <S_SE>
 <D_96/>
 <D_329>800001</D_329>
 </S_SE>
 </S_ST>
 <S_GE>
 <D_97>1</D_97>
 <D_28>8</D_28>
 </S_GE>
 </S_GS>
 <S_IEA>
 <D_I16>1</D_I16>
 <D_I12>000000008</D_I12>
 </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

Idoc to file scenario general query

Hi All,
I know about the basic settings needed for the Idoc to file scenario.
My query is related the idoc /ALE settings.
I have a scenatio wrking in my system where we have configured the port for B type partner and also the port as XML-HTTP
I can not see any DM(BD64) created for it basically.I want to know that in what scenarios the BD64 configuration is required.
Or it is the case that if we define the BD64 then we do not need to configure we20 and we21, it will be auto configured?
Please let me know the use cases for these different configurations if any.
Thanks in advance.
Regards,
Rahul Kulkarni

Hi Rahul,
BD64 uses mostly IDoc to IDoc scenarios because the IDoc consults the distribution model and determines whether any filter objects are specified for a receiver.
WE20 and WE21 (Partner Profile,Port Definition) we have to define in any scenarios where ECC included.
Thanks,
Seshu.

Require a Message mapping for this Logic.

Hi Experts,
I require a Message mapping for this Logic.
In the Source there are 4 fields and, the Target side, the fields should appear like this.
Source Structure- File
Record
|-> Header
Order_No
Date
|-> Item
Mat_No
Quantity
Target Structure-IDoc
IDoc
|-> Header
|-> Segment
Delivery_Order_No
Recv_Date
|-> Item
|-> Segment
Delivery_Order_No
Material_Num
Recv_Quantity.
The Logic is for every Order number an IDOC is generated.And if the Material num matches then the quantity should be added. and important note is that the material numbers are different for every order number. That means if a material number is 2 in the order number A. Then the material number can never be 2 in any of the order numbers.Here is the following with an example for the above scenario.
For example:-
we have
Source Structure- File
Order-no Date Mat_No Quantity
1 01/02/2011 A 10
1 01/02/2011 B 15
1 01/02/2011 A 10
2 01/02/2011 C 10
2 01/02/2011 C 10
3 01/02/2011 D 20
3 01/02/2011 D 10
3 01/02/2011 E 25
Target Structure-IDoc
Delivery_Order_No Recv_Date Material_Num Recv_Quantity
1 01/02/2011 A 20
1 01/02/2011 B 15
2 01/02/2011 C 20
3 01/02/2011 D 30
3 01/02/2011 E 25
So for this example total of 5-Idocs created. That means for this example if Order_No is 1 When the Mat_No is A the quantity gets added. For this Scenario 1 IDoc with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) is generated by adding the quantity field in the Target Side. Similarly if Order_No is 1 when the Mat_No is B then separate IDoc is generated with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) in the Target Side. Similarly, if Order_No is 2 when the Mat_No is C, an IDoc is generated with four Fields 2 in Header(Delivery_Order_No, Recv_Date) and 2 in Item(Material_Num, Recv_Quantity) by adding the quantity field in the Target Side. ike wise the process goes on upto 3.Kindly do the needy..
Thanq very much in advance..
Edited by: Prashanth Bharadwaj on Oct 17, 2011 1:29 PM

Hi Prashanth,
Concatinate the two fields OrderNo and MaterialNo and follow the below logic which will resolve your problem.
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext-->IDOC
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext>splitByEachValue>subString(0,1)-->Delivery_Order_No
formatByExample>collapseContext>SplitByEachValue-->Recv_Date
FormatByExample:
input1:resulrOfSortByKey
input2:concatination>removecontext>sort-->SplitByValuChange
sortByKey:
input1:concatination-->removecontext
input2:date-->removecontext
concatinationOfOrderNo&MaterialNo>removecontext>sort>splitByValueChange>collapseContext>splitByEachValue>subString(1,1)-->Material_Num
formatByExample>sum>Recv_Quantity
FormatByExample:
input1:sortByKey
input2:concatination>removecontext>sort-->SplitByValueChange
SortByKey:
input1:concatination-->removecontext
input2:Quantity-->removeContext
Regards,
Priyanka.

Exception Handling in Message Mapping and Alert

Hello,
1. Pls let me know the concept of Exception Handling and Alerts.
2. Pls provide some blogs for Exception Handling in Message Mapping.
3.What are Alerts and how it help us in XI. Pls provide some blogs for Alert
4.How are Alerts and Exception Handling can be related say for some scenario
Regards

Hi,
Plz check out these blogs of Sravya on Error Handling:
/people/sravya.talanki2/blog/2006/11/22/error-handling-framework-xiout-of-the-box-episode-1
/people/sravya.talanki2/blog/2006/11/23/error-handling-framework-xiout-of-the-box-episode-2
Also check this SAP Presentation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9418d690-0201-0010-85bb-e9b2c1af895b
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Error Handling :
http://help.sap.com/saphelp_nw04/helpdata/en/56/b46c3c8bb3d73ee10000000a114084/frameset.htm
Alerts:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
http://help.sap.com/saphelp_nw04/helpdata/en/56/d5b54020c6792ae10000000a155106/content.htm
BPM:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Working with acknowledgements
regards

Is there pre-configured message mapping for SRM Content?

Hi,
My requirement is to do a message mapping between the SRM Message "Purchase Order Request" and the R/3 Idoc Orders01. Is there a preconfigured message mapping in SRM content or will I have to do it?
I see the generated proxy class from the outbound message interfacePurchaseOrderRequest_Out which will carry the message to XI and my requirement is to map it to the Interface ORDRSP.Orders01 Please let me know if there is a pre-configured message mapping for this ? or is the message mapping between the message "Purchase Order Request" and the R/3 IDOC ORDERS01 to be done by the developer himself?

HI,
There are mappings available in the predelivered SRM content from SAP.
Did you import the SRM content into the repository? If so , you can find this.
www.service.sap.com/ibc -> Integrated Business Content for mySAP SRM->
Hope this helps,
Rgds,
Moorthy
Message was edited by:
Krishna Moorthy P

PDR/Repl.Workbench, Handle 2 Message Types for Materials

Hi there, here in an existing landscape material data gets distributed to a couple of systems with the PDR tool. A custom message type ZMATMAS2 is being used and in UPSC01 the object type MAT is mapped to that ZMATMAS2. Now, I need to connect a new system with PDR and I would like to a new message type, say ZMATMAS_NEW. (to be independen from existing extensions, segment reductions etc.)
What would be the best way to handle different message types for different systems in PDR / UPS?
I thought of creating a new object type in UPSC01, e.g. ZZMAT and mapping it to my ZMATMAS_NEW. But I wouldn't know how to enhance what in the consequence of that, so that PDR / UPS works with two object types for materials.
Any idea?
Regards,
Karsten

Hello Karsten.
that is no problem - that is what the solution was designed for.
You have to define different UPS package types and register them recipient dependant.
kind regards
Marcus Wagler

Context handling in message mapping for an IDoc to File Scenario

Similar Messages

Maybe you are looking for