Issue while posting XML to BAPI_LEAD_CREATE

I am stuck while trying to HTTP post an XML to Gateway Service which calls the BAPI_LEAD_CREATE in SAP CRM. The request is posted from the REST CLIENT In Firefox and i get an non descriptive HTTP 400 error in response
<?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code/><message xml:lang="en">
System expected the element '{&EXPECTED_NAMESPACE&}&EXPECTED_NAME&'</message>
</error>
I am unable to figure what the issue is, because i have used the Standard atom Envelope for the Request Body and have ensured the required data elements are present in the XML string
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<atom:entry
xmlns:atom="http://www.w3.org/2005/atom"
xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices"
xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<atom:content type="application/xml">
<m:properties>
<d:value>xxx@xxxxxx,com</d:value>
<d:scheme_id>Z_CRM_LEAD_FINAL</d:scheme_id>
<d:scheme_agency_id>E61</d:scheme_agency_id>
<d:process_type_1>dmy1</d:process_type_1>
<d:lead_type>dmy1</d:lead_type>
<d:process_type_2>L</d:process_type_2>
<d:lead_type_1>dmy2</d:lead_type_1>
<d:partner_fct>L</d:partner_fct>
<d:title_p>M</d:title_p>
<d:firstname>sriram</d:firstname>
<d:lastname>vasudevan</d:lastname>
<d:city>bangalore</d:city>
<d:street>sjri</d:street>
<d:street_no>20</d:street_no>
<d:country>india</d:country>
<d:region>karnataka</d:region>
<d:tel1_numbr>900-000-002</d:tel1_numbr>
<d:fax_number>900-000-002</d:fax_number>
<d:partner_fct_1>C</d:partner_fct_1>
<d:title_p_1>M</d:title_p_1>
<d:firstname_1>sriram</d:firstname_1>
<d:lastname_1>vasudevan</d:lastname_1>
<d:city_1>C</d:city_1>
<d:street_1>C</d:street_1>
<d:street_no_1>S</d:street_no_1>
<d:country_1>I</d:country_1>
<d:region_1>T</d:region_1>
<d:e_mail>xxx@xxxxxx,com</d:e_mail>
<d:tel1_numbr_1>9</d:tel1_numbr_1>
<d:fax_number_1>9</d:fax_number_1>
</m:properties>
</atom:content>
</atom:entry>
Any help with this is appreciated.

Chandan
Couldn't figure out your reply on the payload, i have instead attached the Metadata for your reference, can you help me structure the payload
... Metadata
<?xml version="1.0" encoding="utf-8" ?>
<edmx:Edmx Version="1.0" xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns:gp="http://www.sap.com/Protocols/SAPData/GenericPlayer" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:sap="http://www.sap.com/Protocols/SAPData">
<edmx:DataServices m:DataServiceVersion="2.0">
<Schema Namespace="Z_CRM_LEAD_FINAL" xmlns="http://schemas.microsoft.com/ado/2008/09/edm">
<EntityType Name="z_crm_lead_final" m:HasStream="false" sap:content-version="1">
<Key>
<PropertyRef Name="scheme_id" />
<PropertyRef Name="scheme_agency_id" />
<PropertyRef Name="value" />
</Key>
<Property Name="row" Type="Edm.Int32" sap:label="Lines in parameter" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="log_no" Type="Edm.String" MaxLength="20" sap:label="Log number" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="process_type_1" Type="Edm.String" MaxLength="4" sap:label="Transaction Type" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="street_no" Type="Edm.String" MaxLength="12" sap:label="Street Code" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="partner_fct_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="tel1_numbr_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="firstname" Type="Edm.String" MaxLength="40" sap:label="First name" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="message_v4" Type="Edm.String" MaxLength="50" sap:label="Message Variable" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="parameter" Type="Edm.String" MaxLength="32" sap:label="Parameter Name" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="message_v2" Type="Edm.String" MaxLength="50" sap:label="Message Variable" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="field" Type="Edm.String" MaxLength="30" sap:label="Field name" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="scheme_id" Type="Edm.String" Nullable="false" MaxLength="30" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="country" Type="Edm.String" MaxLength="3" sap:label="Country Key" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="fax_number" Type="Edm.String" MaxLength="30" sap:label="Fax" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="e_mail" Type="Edm.String" MaxLength="241" sap:label="E-Mail Address" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="number" Type="Edm.String" MaxLength="3" sap:label="Message number" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="scheme_agency_id" Type="Edm.String" Nullable="false" MaxLength="16" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="system" Type="Edm.String" MaxLength="10" sap:label="Logical system (source of message)" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="title_p_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="partner_fct" Type="Edm.String" MaxLength="8" sap:label="Partner Function" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="message_v1" Type="Edm.String" MaxLength="50" sap:label="Message Variable" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="street" Type="Edm.String" MaxLength="60" sap:label="Street" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="lead_type" Type="Edm.String" MaxLength="4" sap:label="Lead Group" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="process_type_2" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="message_v3" Type="Edm.String" MaxLength="50" sap:label="Message Variable" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="lastname" Type="Edm.String" MaxLength="40" sap:label="Last name" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="street_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="title_p" Type="Edm.String" MaxLength="30" sap:label="Title" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="region" Type="Edm.String" MaxLength="3" sap:label="Region" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="lastname_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="region_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="log_msg_no" Type="Edm.String" MaxLength="6" sap:label="Message serial no." sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="type" Type="Edm.String" MaxLength="1" sap:label="Message type" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="country_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="tel1_numbr" Type="Edm.String" MaxLength="30" sap:label="Telephone" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="firstname_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="street_no_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="message" Type="Edm.String" MaxLength="220" sap:label="Message text" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="id" Type="Edm.String" MaxLength="20" sap:label="Message Class" sap:creatable="false" sap:updatable="false" sap:filterable="false" />
<Property Name="city" Type="Edm.String" MaxLength="40" sap:label="City" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="city_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="value" Type="Edm.String" Nullable="false" MaxLength="72" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="fax_number_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
<Property Name="lead_type_1" Type="Edm.String" MaxLength="1" sap:label="Updated info. user data field" sap:creatable="true" sap:updatable="false" sap:filterable="false" />
</EntityType>
<EntityContainer Name="Z_CRM_LEAD_FINAL" m:IsDefaultEntityContainer="true">
<EntitySet Name="z_crm_lead_finalCollection" EntityType="Z_CRM_LEAD_FINAL.z_crm_lead_final" sap:content-version="1" sap:creatable="true" sap:updatable="false" sap:deletable="false" />
</EntityContainer>
</Schema>
</edmx:DataServices>
</edmx:Edmx>
--> ....
Appreciate your help on this.

Similar Messages

Issue while posting the invoice in background using the WF-BATCH user

Hi Friends,
I am facing an issue while posting the invoice in background using the WF-BATCH user. I am using a invoice approval workflow where in when the approver approvers the invoice the invoice document get posted using a background method, which uses BO FIPP and Method POST and i am returning the Message Text to my workflow container from this method. When i see the log an exception is rasied from this method with an error message "V004: You are not authorized to change this document", but WF-BATCH is having SAP_ALL and SAP_NEW authorizations. If i try to post the invoice using the method from my user id it is getting posted. What could be the issue. Please advice.

Hi Sapient,
The Parameter, Roles would be different for the LOGIN USER and WF-BATCH.. So ask your administrator
to set the Roles & Parameters similar to that of LOGIN USER to WF-BATCH.
For further refrence check in SU01 giving the LOGIN USER and then check with WF-BATCH... you would
find the difference...
Hope this would help you..
Good luck
Narin

Error while posting xml file to URL using URLConnection

Hello everyone,
I am facing an issue from long time related to URLConnection. If this would be resolved by your help then I would be very grateful to you.
One application which posts xml file to URL hangs and after waiting for 5 mins it throws 504 error:
java.io.IOException: Server returned HTTP response code: 504 for URL: http:hostname.
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:715)
Same application is running fine without error on another environment from last 5 years. But on another env it is erroring out from the day 1.
We have many workarounds in place none worked.
I tried to use HttpClient from apache but that too hanged at URLConnection.getInputStream() method call.
App is running on iPlanet web server 6.1 using JDK 1.4.0_03
We still dont know why this program hangs at that particular line in only one env but many times it runs fine. That means 30% of the times it posts xml file without error but 70% times it errors out. So our program logic is to retry until post is successful.
Once this issue is resolved we will remove the logic of trying again and agian.
Please provide inputs.
Thanks,
Nitin

The HTTP response 504 means that the server, acting as a gateway, has not received a response from an upstream server in the time it expected.
I think this is problem is due to the remote server that receives the XML and takes too long to return a response to the local application that posted the XML.
Try HttpClient and set the timeout variable of the HttpClient instance used.
Here http://svn.apache.org/viewvc/jakarta/commons/proper/httpclient/trunk/src/examples/PostXML.java?revision=480424&view=markup
a Post XML sample.
NB: HttpClient > setTimeout method is deprecated. See : http://jakarta.apache.org/commons/httpclient/apidocs/index.html for an alternative
Hope That Helps

Issue while posting message to queue

Hi ,
I am getting following exception while posting message into queue.For every new build I am getting this exception and after 2 or 3 times of restart of corresponding OBPM related weblogic server,Issue is getting resolved
A component failed while executing activity '/COM/OU/UserlProcess#Default-3.0/ComponentExecution[PreProcessor]' (BP-method preProcessor) over instance '/COM/OU/UserlProcess#Default-3.0/15141/0'.
Details:
The task could not be successfully executed.
Reason: 'fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Caused by: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Caused by: Connector [MAIN_Q:null:JMS] returned the wrong class [com.tibco.tibjms.naming.TibjmsConnectionFactoryAttributes] for a resource of type [2].
Detail:Connector [MAIN_Q:null:JMS] returned the wrong class [com.tibco.tibjms.naming.TibjmsConnectionFactoryAttributes] for a resource of type [2].
fuego.lang.ComponentExecutionException: The task could not be successfully executed.
Reason: 'fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1091)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1277)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:126)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:84)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
     at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:217)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:203)
     at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:115)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4123)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4013)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4541)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:95)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:324)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:298)
     at fuego.connector.JMSHelper.getSession(JMSHelper.java:75)
     at fuegoblock.msg.DynamicJMS.sendMessage(DynamicJMS.java:145)
     at xobject.Utility.JMSService.writeToAppQueue(JMSService.xcdl:11)
     at xobject.Utility.Notification.sendAuditNotification(Notification.xcdl:19)
     at XXX.ManualProcess.Default_3_0.Instance.CIL_preProcessor(Instance.xcdl:20)
     at XXX.ManualProcess.Default_3_0.Instance.CIL_preProcessor(Instance.xcdl)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1082)
     ... 31 more
Please help how can I resolve this issue
Thanks
Sailendra

I am also getting the same issue. Sailendra, did you resolve the issue?
If not could anyone help us to resolve this issue.
I am using Tibco JMS for queue and I have set 'ConnectionFactory' as Connection Factory Lookup Name value in the external resourse.
Thanks in advance.
Regards,
Ramanan

Document splitting issue while posting MIRO transaction

Hello All
I have a piculiar related to document splitting while posting MIRO entry and this issue started after defaulting the profit center
to the tax gl.
The scenario is like this
While posting a vendor invoice document where there is a difference in the invoice value and stock is allready consumedn
hence system will try to post the difference to the material difference account.
The following is the asccounting entries
01 vendor a/c cr   1000
02 gr/ir a/c dr         800       pc from po document
03 tax g/l                 180       default pc
04 inventory diff       20
the error message
system is not able to determine the profit center at line item 04 and message is
Balancing field "Profit Center" in line item 004 not filled
The document splitting settings are all standards related to vendor invoice ..................
One important point to be noted here is that this issue is come after defaulting the profit center at tax gl.
But we cannot remove those default pc also.
Can be their any solution on this
Kindly suggest
Thanks

Hi
In addition to my previous mail i want to add that
i tried to add even expense item category to splitting rule of business transaction and transaction variant.
Even then it doers not work.
other then is as per standard document splitting rule the expense item category is not included in invoice verication buisness transaction.
Thanks
alok

Facing issue while reading XML file 'LPX-00217: '

Hi Gurus,
I am facing one issue while reading the xml file in the one my 11g database instance. The same file if I ran in another instance then it is working fine for me.
I presume it will be related to NLS character. Please help me in finding out character set.
And the issue where I am getting instance character set is 'US7ASCII', and I am not getting this issue in another instance where the character set is 'UTF8'.
And here is the issue I am getting when I was trying to load that file.
Error Occurred :=ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML
processing
LPX-00217: invalid character 150 (U+0096)
Error at line 1
Pls help me in debugging this issue.
Regards,
Nagendra
Edited by: 838961 on Jul 12, 2011 9:32 PM

Hi,
Pls help me in debugging this issue.There's not much to debug actually.
The US7ASCII charset stores 7-bit characters, but you're trying to insert a value out of range (150). So that's expected behaviour.
There were some "tricks" to allow that on some versions, using NLS settings, but it's definitely not the clean way to do it so I won't develop.
The best thing you have to do is to migrate to character set AL32UTF8, which is fully compliant with XML.

Read Time out error while posting XML file

Hi
While posting the XML file from .NET application to XI I am getting following error :
com.sap.engine.services.httpserver.exceptions.HttpIOException: Read timeout. The client has disconnected or a synchronization error has occurred. Read 62127 bytes. Expected 75283.
            at com.sap.engine.services.httpserver.server.io.HttpInputStream.read(HttpInputStream.java:186)
            at java.io.FilterInputStream.read(FilterInputStream.java:111)
            at java.io.PushbackInputStream.read(PushbackInputStream.java:161)
            at java.io.FilterInputStream.read(FilterInputStream.java:90)
            at com.sap.aii.messaging.net.MIMEInputSource$MIMEReader.readContent(MIMEInputSource.java:683)
            at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:342)
            at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
            at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:358)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
            at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Earlier I incresed the PROCTIME as 600 secs ( OSS Note 824554 ) -->
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=600,PROCTIMEOUT=600
In this case do I need to increase this parameter value again & what should be the optimal value which will not effect the performance of the system too.
Best Regards
Lalit Chaudhary

hi Lalit,
Check the OSS note(807000) and see if it helps you....
Re: Calls to Webservice published by XI getting lost
hope it helps,
regards,
Anu

Dummy Profit center issue while posting the transaction in FB60

Dear SAP friends,
We have implemented ECC6.0 version,
I have the below issue:
I am posting the document in FB60 transaction: after simulating the document system is throwing the error "Profit center 9937/FIREPRODMY does not exist for 14.08.2009"
Message no. KM700
Document spilitting active at Business area level..
In 0KE5( maintain controlling area settings) I have not given the Dummy profit center.
Eventhough it is asking for Dummy profit center while posting, Please let me know apart from the 0Ke5 settings do i need to remove the dummy profit center anywhere in the Config.
I have not maintained any settings in FAGL3KEH, 3KEH and OKB9.
No sunstitutions are active in the system.
Please let me know from where i need to remove the dummy profit center.
My client going live on 17th Aug 2009.
Regards,
Anand

Hi,
Check the validity period of the Profit Center 9937/FIREPRODMY. The valid from period should have the date same or earlier than 14.08.2009
If not then change the profit center master data to be valid from an earlier date (Tcode KE52). Steps-
KE52 - Profit Center FIREPRODMY
Click Change Validity Period (Ctrl +F1)
Valid from - put a date earlier or equal to 14.08.2009
Click Activate (Shift + F1)
Thanks,

Issue while posting billing doc to account

Hi All,
There is an inssue with an inbound idoc, actually when an inbound idoc is recieved, sales order is created automatically, but while posting the billing document to account it shows an error, pricing error in item, and when we check the the data in idoc we are getting it selects the wrong Relational owener id which are not maintained, so i need to find out in which exit i can the logic for that please help me.
The error is not consistent , sometime it works and sometime does not.
see the below
''When we change this Relational Owner from ‘F’ to ‘J’, they are able to posting their accounts. I want to know from where this ‘F’ is getting populated because we didn’t maintain ‘F’ anywhere. Need to know from where –F is getting populated in the sales order''.
Thanks
Ik

Hello Khan ,
You need to solve this issue on your own by debugging. I suggest you to set a watch point on the filed i,e variable-name = '-F' to know how it is being populated.
Thanks

Dealer Excise Invoice-Issue while posting MIRO

Dear All,
Today i was doing Domestic procurement with Dealer for Gas Cylinder. In PO we entered total value which includes Excise amount also (1000+103)& VAT @ 14% (154,42).
While doing GR i selected as Only captured excise inv, checked MRP indicator.
Changed the bse value to 1000, entered BED as 100, E Cess as 2 & SEcess as 1.
The accounting entries were correct, Inventory is posting with Rs 1000
Posted excise invoice in J1IEX, the values were coming from GR, its correct and the acc entries were also OK with 103 Cenvat clearing acc Cr & Excise acc Dr.
While posting MIRO, I am facing problems...
In line item i am getting as 1103 Base value...
VAT is calculating on (1103+103) @ 14% 168.84,
so total value is 1271.84
When i simulate, its showing
Vendor 1271.84 Cr
GR/IR clg acc 1000 Dr
Material 103 Dr
VAT 168,84 Dr
There is no cenvat clearing account here
Please help me how to resolve this.
Regds,
CB
When i simulate

Hi,
have you mainatin 100% setoof condition check it it should be there
check MIRo posting date and excise invoice posting date
check condition record validity in FV13
Regards
Kailas Ugale
Edited by: kailasugale on Feb 10, 2012 12:01 PM

SAP HUM Issue while Posting TO.

Hi There,
I have issue while doing picking for HUM with Nested HU.
Scenario :
- We have Nested HU with 11 Box packed on it. (10 Box Batch A + 1 Box Batch B).
- I have an outbound delivery for 1 material with split batch. (Batch A and Batch B). while doing picking against outbound delivery, i created a TO. System did proposed me a Nested HU for picking. I created a Pick HU by LH01 as well to repack what i want to pick. All worked fine till now.
- Now I want to pick 1 box of Batch A and 1 Box of Batch B.
- I can not do that. I am keep getting error i do not have enough material on nested HU, how ever i do!!!
- IFFFF,
I do have only 1 Batch to pick ( NO Split delivery), from same Nested HU, i can always pick 1 box. Either Batch A or Batch B with full QTY. I only get error for Batch split scenario for picking.
Can any one help me on that?
Smit.

You should debug your program and see where exactly and what causes this behavior.
In this way you will have a cause of the issue and could be able to retrace it back to the root cause of the problem.
Just one more thing to clarify... Your TO is created and the system did propose your nested HU for picking but when you pick from it, you get the error message?
Can you please write the exact error message number and description?

Issue while posting physical inventory document

Hi Team,
While posting a physical inventory document system is giving error message saying that
HU exists at another point in the warehouse. Clear the HU first
Message no. /SCWM/GM751
here is my scenario: As per the system bin is empty, while doing physical inventory we found and counted one HU in the same bin. while posting the same physical inventory document we are getting the above error message. as per the system this HU available in some other bin.
could you please let us know is there any process which i am missing before posting the PI document.
while posting the PI document is it not possible automatically HU get move from one bin to other bin?
Thanks
Mastan

Hi kmastanrao
All above suggestion given need to check.
1. Check HU available in WH. In EWM monitor and HU details.
And after finding the status of HU and use as you need in your process.
second if needed I can provide HU table in EWM which can be used.
Regards
Suraj

Error while posting XML from a scheduled transaction to another transaction

When I try posting an XML from one transaction to another in a different project by calling it as a webservice, it doen't hit the other transaction.
I see this in the Netweaver error logs:
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)
at java.util.zip.ZipFile.<init>(ZipFile.java:127) [see details]
XML AssignXml Parse Error
[EXCEPTION]
org.xml.sax.SAXParseException: Premature end of file.... [see details]
AND
[Fatal Error] :-1:-1: Premature end of file.
More interestingly it happens ONLY when I schedule the parent transaction, when I trigger it manual everything works fine.
Any help appreciated.

Hi Srinivas,
I see that this post was marked as answered. Could you please elaborate on how this problem was fixed?
I am experiencing a similar issue:
I am trying to get the Active Portal application running in MII 12.1.7 (also 12.1.8) and all went well up to the point where the ActivePortalMonitor transaction is scheduled. In the logs I also receive the org.xml.sax.SAXParseException.
The culprit is the XMLQuery block in that txn. Just like with your situation, when ran from workbench it works; when scheduled it doesn't.
I tried replacing the XMLQuery with other blocks that get the same result, i.e. XMLLoader or HTTPLoader + StringToXMLParser; and in all cases the XML fetching element bombs out.
I also built a simple txn that does an XMLQuery on another txn and then dumps the output in a file. Same thing: when run from workbench it runs fine; from scheduler it gives "SAX" error
I would post the specific error log, but it is always varying, here is one example:
[ERROR] [Untitled_0]org.xml.sax.SAXParseException: Open quote is expected for attribute "DIR" associated with an element type "HTML".
Any help/hints are much appreciated
Kind Regards,
Fanie

Decimal Issue while posting annual salary using HCM P&F

Hello All
We are facing a strange problem while updating the Annual Salary of Infotype 0008 using HCM P&F. User in the form can enter a wage type amount, based on this wage type amount the annual salary is getting calculated by the std. way.
Now the problem here is, say we are passing Hourly wages as 55.000 USD3, the annual salary should have been updated as 114400.00 USD (i.e. 55 * 2080 Hours Annually). But after the posting when we see the annual salary amount it is displayed as 11440.00 USD (Strange!! It is divided by 10 ). But the wage type amount is properly displayed as 55.000 USD3 in PA20. All the other infotypes are updated correctly with the new pay structure and work schedule details correctly.
Appreciate your help, if any of you have come across this issue before.
Thank you.
Regards
Ranganath

hahahahahahaha
Been down this road before.
Pretty much it is exactly as said....decimal for currency issue. Some currencies use 2 decimal places...some use 4...and better yet, SAP allows you to even configure your own if needed.
Now, how did WE solve this. We tore apart (debugging) the actual code SAP uses in PA30 when showing/editting/updating Basic Pay. You will see in there how they work the "magic". Oddly.....the look at the decimal setting, multiply it out in the background to store correctly but pull a "switch-a-roo" on the front end to display it correctly as the user would expect (ie 4 decimals for example). It's pretty crazy stuff.
But we got it working....via code in our own generic service......and it worked like a charm.

Issue while posting using goods issue for delivery type NL

Hello Experts,
I have created an outbound delivery for an intra-company transfer (within same company code) between two plants. The delivery type in NL (replinishment delivery)
When i am trying to post the goods issue from supplying plant, I am getting following error
"Account type K is not defined for document type WL".
Delivery type NL should not be used to issue stock to vendor but I am not issuing it to any external vendor , issuing the stokc only to a receiving plant.
Please help to understand why i am getting this error.
Regards,
Nish.

Hi,
If you are doing an STO Scenario, Check whether you have created the supplying plant as a vendor.
The Vendor Account group should be plants.
Also check whether you have given the plant in the vendor master Purchasing Data - Extras tab in the menu click on add purchasing data & check.
If you haven't assigned this, do the same & create a fresh STO & check.
Hope it will work.
Thanks & Regards,

Issue while posting XML to BAPI_LEAD_CREATE

Similar Messages

Maybe you are looking for