Calculating No. of records XI message payload

Hello,
Can somebody help me out to calculate no.of records in terms of XML tags in XI message payload.
I have a scenario File->XI->ABAP proxy. File content conversion is used in FTP adapter. So my requirement is to count no. of records come from to XML tags.
Thanks in advance.
Best regards,
Jilan Bhasha
Message was edited by:
Jilan Bhasha.P

Hi Jilan,
Actually where do you want to get this count..
In sender file adapter config , we have option counter..
-- or you can have a UDF to count the no of msgs ..
-- you can use count function to root. that can be assigned toone target field..
Recordsets per Message see in the below link
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Hope this helps. Do get back to me in case you need any more details...
Regards
Kiran..

Similar Messages

Sending the fault message payload to sender using BPM.

I have the scenario where BPM splits a file into multiple record and each record calls webservice.
For a successfull call a success response is generated by web service . For a failed transaction a fault message is sent back which needs to be delivered to the sender's mail ID.
I am not able send the fault message payload which contains the error message details to sender ..
Please suggest what can be done for such a scenario. Is there any way by which error details can be sent to sender?
Edited by: trisha.b on Nov 28, 2010 7:23 PM
Edited by: trisha.b on Nov 28, 2010 7:29 PM

Hi,
Check the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/22017.. [original link is broken] [original link is broken] [original link is broken]
You can handle the exception on your web service and model a Notification task so that you can send e-mail notification to the sender in case of exception
Regards, Anil

Error while processing message payload Element 'CategoryCode&#39

Hi Experts,
I am trying to integrate SAP ECC with TM. I have transferred the sales order from ECC to TM, but its not triggering order based transportation requirement (OTR) instead giving an error Error while processing message payload Element 'CategoryCode&#39 and all the xml messages are stuck in inbound queue. The screen shot of the issue is as appended herewith. Please advise.
Thanks & Regards,
Aunkur De

Hi Aunkur,
The issue will generally come when a mandatory field in XML which you are not sending either or missed.
Please check if all mandatory fields are mapped properly.
Best regards,
Rohit

Error while processing message payload Element PI SXMB_MONI (ECC to TM)

Dear Experts,
while processing an XML message in TM using receiver interface IntracompanyTransportationRequestRequest_In , we encounter an error message.
<SAP:Stack>Error while processing message payload Element 'StockTransportOrderReferenceIndicator' missing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
ssee screenshot attached.
The field StockTransportOrderReferenceIndicator cannot be located in ECC and I cannot find what the system is expecting to populate here.
Can somebody propose an approach on how to investigate into this error message for the solution?
thanks a lot
Salvador

Hi Salvador,
Thanks for your reply. We were able to fix that issue. As of now we have managed to send sales order to TM but getting the following error. Messages are getting failed in SAP TM. Even if the product exists in the system (TM) still the error message persists. I have CIFed location, business partner, product from ECC and everything exists in SAP TM with the same business system group. Kindly advise. Did you happen to face any similar kind of issue during your implementation ?
Thanks & Regards,
Aunkur De

PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.
Here is an example:
12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
12/12/11 4:39:06 PM request received for a channel
I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.
Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

Hi,
When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

Message payload?

Hi,
What is a message payload in XI?
Thanks.

Hi...
Payload is nothing but the data(data type) provided by u
and which is displayed in XML format...
The payload is the actual contents (business data) of a message in the Exchange Infrastructure(this is from the help).
Cheers,
Raghavesh

How we can mention varible substitution for diffrent message payloads

Hi,
How we can mention varible substitution for diffrent message payloads,
My sceanrio like following,
According the Outbound idoc message,based on the condition the messages to be split into 9 diffrent files.The sender message may or may not satisfied the condition to one or two messages or all messages.
I done the mapping 1:N multimapping in messagemapping & Interface mapping too.
In reciever file adapter i put the variable substiution like as fallows.
Variable Refrence
Name-- -
Filename -- payload:message_type_1,1,Segment1,1,Segment2,1,Field_1,1
<b>How we can mention variable substitution for remaining messages in the same communication channel.my message type names are diffrent for all 9 messagetypes.</b> Any ideas pl forward..,
When i am testing this scenario,able to processing a one file but the file is not placed in the specified target & gives the follwing error:
'Conversion configuration error: Unknown structure 'ns1:message_type_2' found in document', probably configuration error in file adapter (XML parser error)'.The file is
In this case Idoc data satisfied the one message condition only.
If any ideas & suggestions ..?

Hi Anjan
You could always put the "FileName" and "Directory" names into the Dynamic Configuration using a UDF in the map - possibly using a value mapping table to determine the correct values. Then simply reference "%Directory%" and "%FileName%" in the file adapter. This way you do not have to reference payload variables and you set the names in the map. You will need to tick the box for "use adapter specific message attributes" in the file adapter. you UDF code will look something like
String dir = "/path";
String fil = "filename.txt";
DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");
conf.put(key,dir);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
conf.put(key,fil);
- Stephen

Filtering of records in Message Mapping

I am facing problem during filtering record in message mapping. My message comes from R3 and should be sent to one business service in entirety and should also be sent to another business service in part. To resolve this I created a message map for selecting record based on some conditions but this creates empty XML nodes wherever condition is not satisfied. Everything works fine but the scenario fails at the end while trying to convert XML to text using file adapter. The error is Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)

Hi Rajesh,
This scenario you are trying can be done using CONDITIONAL RECEIVER DETERMINATION and RB SPLIT, where you can basically have one sender and two receivers.
To do this without using a BPM.
1. Create your mapping program that will map the information from the source file
into the destination idoc. This has to be a 1:N split. Just make sure that the destination message type and message interface are are of occurrence N.
2. Also, you will have 2 destination interfaces and 2 interface mapping, one for the IDOC and one for the mail.
Now, there are a few essential steps in your configuration,
1. In the receiver determination, specify the 2 receiver systems, one for your IDOC and the other for your MAIL.
2. Now, you will have a condition window. Just type the condition on the basis of which the receiver has to be determined for the mail and the idoc business system. Just remember that the condition can be specified only for the source message.
3. In the Interface Determination, you have an option called RB CLASSIC and RB SPLIT. To do a 1:N split, you will have to do a RB_SPLIT.
And since you wanted to covert the XML format to text format you require content conversion at the receiver adapter end, for that please go through these links below. It clearly explains your requirement.
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
I hope I have answered your query.
Regards,
Abhy
note: do reward points for the helpful answers.

Sender File Adapter cannot send single record per message ?

Hi,
I have scenario flat file to jdbc. but then why the sender file adapter didn't split the record to become single record per message eventhough i have set it in "Recordsets Per Message" = 1. ?
Document Name               MT_APINVOICE
Document Namespace          urn:file:jdbc:apivinvoice
Document Offset               8
Recordset Name               INPUT
Recordset Namespace
Recordset Structure                          RECORD,*
Recordset Sequence                          Ascending
Recordset per Message          1
Key Field Name
Key field Type               String
RECORD.fieldFixedLengths     10,5,10,10
RECORD.endSeparator     'nl'
RECORD.fieldNames          F1,F2,F3,F4
Please advise
Thank You and Best Regards
Fernand

>>but then how to make for example more then 1 records per message.
like 10 records per message. should i set RECORD,10 ?
That is right. Just try it out yourself.
@Shesagiri,
Number of record is decided by the parameter Recordset structure and number of recordset with in a message is decided by Recordset per Message.
Regards
Jaishankar

Problem in Edit Message Payload in AE

Hi all,
actually we have a problem with editing the message payload of a failed message in the adapter engine.
Messages Editor shows "The version you want to edit is locked"
Log in NWA shows "EditorDynPage: loadMessage()
Thrown:
com.sap.aii.mdt.api.exceptions.OperationFailedException: VersionAlreadyLockedException in Method: AdapterFrameworkMonitoringBean: getTransferMessage( Query ). The version you want to edit is locked. Message: Version 1 of message 4eb86ecc-fb6b-0c10-e100-80000a93147c(INBOUND) is already locked for editing.; To-String: com.sap.engine.interfaces.messaging.api.version.VersionAlreadyLockedException: Version 1 of message 4eb86ecc-fb6b-0c10-e100-80000a93147c(INBOUND) is already locked for editing."
How to delet te lock, the nwa => problem management => locks shows no locks?
regards Ralf

Hi,
In NWS, you should also have a tab "Database Locks". See detail in this [SAP help|http://help.sap.com/saphelp_nwpi711/helpdata/en/48/b2e0156b156ff4e10000000a42189b/content.htm].
regards.
Mickael

Cannot map control record values from payload w/XSLT after SP13 upgrade

Hi!
Since we upgraded to SP13, the mapping of control record values form the XML payload to the IDOC control record (File->XI->IDOC scenario) no longer works if the mapping is done via XSLT. It works if the XI graphical mapper is used. The XSLT used is the same pre and post upgrade, but worked fine previously.
[ Apply Control Record Values from Payload is checked in the IDOC adapter comm channel. ]
Has anyone else experienced this? Am looking for any inspiration
Cheers
Duncan

Are you sure the xslt file is still there?
Maybe some non-compliance was corrected in later SP and your XSLT was using that non-compliance.
If you post the XSLT we could try to point out any possible errors.
Regards,
Henrique.

Wsdl validation fails for request message payload from custom schema

Hello. I am having a problem which I cannot seem to work around. I have defined a schema to serve as a template for the request message payload of a bpel process. The schema is very simple:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:logininfo="http://sru/logininfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru/profile" targetNamespace="http://sru/logininfo" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:import namespace="http://sru/profile" schemaLocation="http://sru/profile.xsd"/>
     <xs:element name="logininfo" type="logininfo:logininfoType">
          <xs:annotation>
               <xs:documentation>Needed information for SRU Login</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="logininfoType">
          <xs:all>
               <xs:element name="email" type="sru:emailType"/>
               <xs:element name="password">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="32"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="product" type="xs:string"/>
               <xs:element name="ip" type="sru:ipType"/>
               <xs:element name="timestamp" type="xs:dateTime"/>
               <xs:element name="xpath" type="xs:string"/>
          </xs:all>
     </xs:complexType>
</xs:schema>
(The schema depends on another, which I have placed at the end of this message).
I import it into the bpel process designer with no problems.
Upon defining the payload of the request message type to be the {http://sru/logininfo}logininfoType, the WSDL file does not validate anymore:
Validating WSDL...
Validating E:\OraBPELPM_1\integration\jdev\jdev\mywork\SRU\BPELProcess5\BPELProcess5.wsdl
Schema type not found: QName(http://sru/logininfo, logininfoType)
Validate WSDL: has errors.
Any ideas?
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="http://sru/profile" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="http://sru/profile" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:schemaURL="http://sru/profile.xsd">
     <xs:annotation>
          <xs:documentation>Joel SalmerÃ³n Viver</xs:documentation>
          <xs:documentation xml:lang="en">General purpose internet profile schema</xs:documentation>
     </xs:annotation>
     <xs:simpleType name="emailType">
          <xs:restriction base="xs:string">
               <xs:maxLength value="255"/>
               <xs:pattern value="[a-z0-9]([a-z0-9\._][a-z0-9]+)*@[a-z0-9]([a-z0-9\.\-][a-z0-9]+)*\.[a-z]{2,6}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ipType">
          <xs:restriction base="xs:string">
               <xs:pattern value="((\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])\.){3}(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="labelType">
          <xs:restriction base="xs:string">
               <xs:maxLength value="32"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:complexType name="addressType" xdb:SQLType="ADDRESSTYPE" xdb:SQLSchema="SRU">
          <xs:all>
               <xs:element name="lines" type="linesType" minOccurs="0" xdb:SQLName="lines" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                    <xs:key name="linesKey">
                         <xs:selector xpath="line"/>
                         <xs:field xpath="@num"/>
                    </xs:key>
               </xs:element>
               <xs:element name="city" xdb:SQLName="city" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="64"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="postalcode" xdb:SQLName="postalcode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="16"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="countrycode" xdb:SQLName="countrycode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:length value="2"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
          </xs:all>
          <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
          <xs:attribute name="verified" type="xs:boolean" use="required" xdb:SQLName="verified" xdb:SQLType="RAW"/>
     </xs:complexType>
     <xs:complexType name="lineType" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="num" type="xs:positiveInteger" use="required" xdb:SQLName="num" xdb:SQLType="NUMBER"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="loginType" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU">
          <xs:all>
               <xs:element name="registered_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="registered_date" xdb:SQLInline="true"/>
               <xs:element name="lastlogin_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_date" xdb:SQLInline="true"/>
               <xs:element name="lastlogin_ip" type="ipType" minOccurs="0" xdb:SQLName="lastlogin_ip" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <xs:element name="lastlogin_time" type="xs:time" minOccurs="0" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_time" xdb:SQLInline="true"/>
          </xs:all>
          <xs:attribute name="product" use="required" xdb:SQLName="product" xdb:SQLType="VARCHAR2">
               <xs:simpleType>
                    <xs:restriction base="xs:string">
                         <xs:maxLength value="32"/>
                    </xs:restriction>
               </xs:simpleType>
          </xs:attribute>
          <xs:attribute name="status" type="xs:integer" use="required" xdb:SQLName="status" xdb:SQLType="NUMBER"/>
     </xs:complexType>
     <xs:complexType name="addressesType" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU">
          <xs:sequence>
               <xs:element name="address" maxOccurs="unbounded" xdb:defaultTable="PROFILE_ADDRESSES" xdb:SQLName="address" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:defaultTableSchema="SRU" xdb:SQLCollType="address360_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                    <xs:complexType xdb:SQLType="address358_T" xdb:SQLSchema="SRU">
                         <xs:complexContent>
                              <xs:extension base="addressType"/>
                         </xs:complexContent>
                    </xs:complexType>
               </xs:element>
          </xs:sequence>
          <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
     </xs:complexType>
     <xs:complexType name="phonesType" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU">
          <xs:sequence>
               <xs:element name="phone" type="phoneType" maxOccurs="unbounded" xdb:SQLName="phone" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="phone363_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
          </xs:sequence>
          <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
     </xs:complexType>
     <xs:complexType name="loginsType" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU">
          <xs:sequence>
               <xs:element name="login" type="loginType" maxOccurs="unbounded" xdb:SQLName="login" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="login366_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                    <xs:key name="loginKey">
                         <xs:selector xpath="."/>
                         <xs:field xpath="@product"/>
                    </xs:key>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="phoneType" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU">
          <xs:simpleContent>
               <xs:extension base="phonenumberType"/>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="profileType" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU">
          <xs:all>
               <xs:element name="firstname" xdb:SQLName="firstname" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="64"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="surname1" xdb:SQLName="surname1" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="64"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="surname2" minOccurs="0" xdb:SQLName="surname2" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="64"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="gender">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:length value="1"/>
                              <xs:enumeration value="M"/>
                              <xs:enumeration value="F"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="alt_email" type="emailType" minOccurs="0" xdb:SQLName="alt_email" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <xs:element name="addresses" type="addressesType" minOccurs="0" xdb:SQLName="addresses" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                    <xs:key name="addressesKey">
                         <xs:selector xpath="address"/>
                         <xs:field xpath="@label"/>
                    </xs:key>
                    <xs:keyref name="addressRef" refer="addressesKey">
                         <xs:selector xpath="."/>
                         <xs:field xpath="@main"/>
                    </xs:keyref>
               </xs:element>
               <xs:element name="phones" type="phonesType" minOccurs="0" xdb:SQLName="phones" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                    <xs:key name="phoneKey">
                         <xs:selector xpath="phone"/>
                         <xs:field xpath="@label"/>
                    </xs:key>
                    <xs:keyref name="phoneRef" refer="phoneKey">
                         <xs:selector xpath="."/>
                         <xs:field xpath="@main"/>
                    </xs:keyref>
               </xs:element>
               <xs:element name="language" type="xs:language" xdb:SQLName="language" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
               <xs:element name="logins" type="loginsType" minOccurs="0" xdb:SQLName="logins" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                    <xs:key name="loginsKey">
                         <xs:selector xpath="login"/>
                         <xs:field xpath="@product"/>
                    </xs:key>
               </xs:element>
               <xs:element name="origin" minOccurs="0" xdb:SQLName="origin" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:annotation>
                         <xs:documentation>iso3166 a2 country code</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:length value="2"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="creation_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="creation_date" xdb:SQLInline="true"/>
               <xs:element name="modified_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="modified_date" xdb:SQLInline="true"/>
               <xs:element name="password" xdb:SQLName="password" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="32"/>
                              <xs:pattern value="[a-zA-Z0-9]+"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="hint" minOccurs="0" xdb:SQLName="hint" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="32"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="additional" type="xs:anyType" minOccurs="0">
                    <xs:annotation>
                         <xs:documentation>future expansion</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:all>
          <xs:attribute name="email" type="emailType" use="required" xdb:SQLName="email" xdb:SQLType="VARCHAR2"/>
          <xs:attribute name="active" type="xs:boolean" use="required"/>
     </xs:complexType>
     <xs:complexType name="phonenumberType" xdb:SQLType="PHONENUMBERTYPE" xdb:SQLSchema="SRU">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:element name="profile" type="profileType" xdb:defaultTable="PROFILES" xdb:SQLName="profile" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU" xdb:defaultTableSchema="SRU"/>
     <xs:complexType name="linesType" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU">
          <xs:sequence>
               <xs:element name="line" type="lineType" maxOccurs="unbounded" xdb:SQLName="line" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="line354_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>

IT would help if the people that are working this issue would post the resolve of their problems. Every post I see with this problem someone from oracle replies with needing the source project to replicate the issue and the thread dies....

Table for XI (PI) message payload content?

Hello Colleagues,
I need to know in what table I am able to find the Payload what is displayed normally under SXMB_MONI for different message processing over XI.
We need to archive (only) payload content for special interfaces in a usefully way.
Many thanks in advance!
Regards,
Jochen

Hi Sudhir,
Many thanks for the providing informations.
During my investigation I found similar information.
So, I afraid too that where is no easy way for export message payload.
Maybe the XML Data Archiving process could be here an answer but i haven't try it before.
Documented at "XML Data Archiving: Configuration Guide for ABAP Applications".
Many thanks for support Sudhir!
Regards,
Jochen

JMS Message Selector on Message Payload

Hi,
I have a requirement where in;
A JMS adapter consumes messages from an AQ JMS Topic. We need to make selective dequeue from the Topic. Is that possible to make use of the message selector option on the 'message payload'?
Message selector works on JMS Header and Properties as far as I know.
Any insight on this would be of great help :-)
Thanks,
Manoj Nair.

It's like almost a month to get a response for such a generic JMS functionality. Looks like the Oracle SOA user base is really low. Anyone with a working example reference.
Thanks

Extracting Value from Message Payload of the Failed Messages

Hi Experts,
We are working on PI 7.0. We have an asynchronous scenario from JMS to IDOC. Vehicle related data is being sent to SAP.
We have a requirement where in we have to extract the vehicle commission number (a field in message payload) of all the failed messages in sxmb_moni(mapping failure).
Is there a way we can achieve this? Can we write some OS level script to the same.
If yes please help me out here.
This is a critical issue.
Kindly advice.
Regards,
Pooja

Hi Pooja,
We have done something similar, but instead of the Vehicle Comm Num, we just retrieved our Transaction ID. Please see the links below. These will send out an email if there was an issue with the message mapping.
Customize E-Mail Body and Subject in Alerts in SAP PI 7.31 – Java Stack Only – Part 1 – ESR
Trigger customized email on error in PI
XI Alerts from UDF using file adapter.
Trigger one alert per failed message
How to send variable data through alert mail without BPM
Raise Alert and also Execute the message
Regards,
Jannus

Calculating No. of records XI message payload

Similar Messages

Maybe you are looking for