RPC calls to Operations with complex types is it possible?

Using Remote Procedure Calls, and Document Literal Wrapped SOAP Messages
I have a complex type called
<customerCall>
<custId>
<custPhone>
<custName>
<custCat>
<custIssue>
<custOperator minoccurs = 0>
<custEnrollDate minoccurs = 0 >
I have an operation called getFirstAvailableOperator(currentCall) where current call is an instance of the customerCall type? Where getFirst AvailableOperator returns the complex type customerCall?

Similar Messages

Problem in calling a WS with complex type

Hi all...
I have to invoke a WS that has as input type a complex type defined in the wsdl...
<complexType name="LoginInfo">
- <sequence>
<element name="appCode" nillable="true" type="string" />
<element name="login" nillable="true" type="string" />
<element name="passwd" nillable="true" type="string" />
</sequence>
</complexType>the soapui request looks like this:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://com.susan/SusanWS/types">
   <soapenv:Header/>
   <soapenv:Body>
      <typ:LoginWebService>
         <LoginInfo_1>
            <appCode>WEB_SERVICES</appCode>
            <login>root</login>
            <passwd>root</passwd>
         </LoginInfo_1>
      </typ:LoginWebService>
   </soapenv:Body>
</soapenv:Envelope>in my java code I'm trying to call it with:
Service service = new Service();
            Call call = (Call)service.createCall();
            call.setTargetEndpointAddress( new URL( wsEndpoint ) );
//            call.setOperationName( wsMethod );
            call.setOperationName( new QName("http://com.susan/SusanWS/types",wsMethod));
            call.addParameter( "LoginInfo_1", Constants.XSD_ANYTYPE, ParameterMode.IN );
//            call.addParameter( "appCode", Constants.XSD_STRING, ParameterMode.IN );
//            call.addParameter( "login", Constants.XSD_STRING, ParameterMode.IN );
//            call.addParameter( "passwd", Constants.XSD_STRING, ParameterMode.IN );
            String[] params={appCode, login, passwd};
//            call.setReturnType( Constants.XSD_INT );
//            Object retval = call.invoke( new String[] {appCode, login, passwd} );
            Object retval = call.invoke( new Object[] { params } );doing so..it doesn't work...the first problem I can see...is that I don't assign a parameter name to the 3 strings I pass in the param array...
anybody has a tip to give me on how to solve this problem?

solved...
I imported the wsdl into Intellij idea...which created all the needed classes, interfaces,...and used service locator and endpoint binding stubs...

Assign error with complex type return message

Dear all,
I have an axis web service with complex type return message. When I invoke the web service, and try to assign one element of the result to other variable, it fails with following error message(BPEL Fault:{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure{}
The invoking web service and assignment BPEL source is as follows:
<invoke name="registerConference" partnerLink="conferenceCenter" portType="tns:ConfArrangementPort" operation="Conference_Register" inputVariable="registerInput" outputVariable="registerOutput"/>
<copy>
<from variable="registerOutput" part="Conference_RegisterReturn" query="/Conference_RegisterReturn/confcity"></from>
<to variable="bookHotelInput" part="si" query="/si/city"/>
</copy>
I tunneled the response SOAP message:
==== Response ====
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Date: Sun, 31 Oct 2004 08:28:27 GMT
Server: Apache Coyote/1.0
Connection: close
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:Conference_RegisterResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://conference.sjtu.edu">
<ns1:Conference_RegisterReturn href="#id0"/>
</ns1:Conference_RegisterResponse>
<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:ConfInfo" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="http://conference.sjtu.edu">
<confcity xsi:type="xsd:string">star</confcity>
<confend xsi:type="xsd:string">20041120</confend>
<confstart xsi:type="xsd:string">20041116</confstart>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
==============
However, when i check the invoke activity audit trail, it return the following info:
<messages>
<registerInput>
<part xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="gi">
<gi xmlns="http://conference.sjtu.edu">
<attendeename xmlns="">ss</attendeename>
<confname xmlns="">hh</confname>
</gi>
</part>
</registerInput>
<registerOutput>
<part xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="Conference_RegisterReturn">
<ns1:Conference_RegisterReturn xmlns:ns1="http://conference.sjtu.edu" href="#id0" />
</part>
</registerOutput>
</messages>
The detailed value of the return message lost, only leaving the href. Can I find the desired value again? should I try another XPATH expression? should I parse the result from the SOAP message directly? Or it's a problem of the system itself?
Hope you can do me a favor, thanks.

From Axis's user guide: RPC services default to the soap section 5 encoding rules, objects will be encoded via "multi-ref" serialization. Document services do not use any encoding (so in particular, you won't see multiref object serialization or SOAP-style arrays on the wire)
May be I should try document service style instead of RPC. Thanks for your reply.

WCF Service as Data source in SSRS report with Complex Types

Hi All,
I have a requirement where we are suppose to use WCF service as datasource in SSRS. I was able to do that when the WCF response type was simple.
Now the requirement have changed where the response type is complex . I couldn't figure out a way of accessing WCF with complex types.
Any pointer will be of great help as I couldn't find any related articles for this kind of scenario.
Raj

Hi Raj,
WCF uses a serialization engine called the Data Contract Serializer by default to serialize and deserialize data (convert it to and from XML). All .NET Framework primitive types, such as integers and strings, as well as certain types
treated as primitives, such as DateTime and XmlElement,
can be serialized with no other preparation and are considered as having default data contracts. Many .NET Framework types also have existing data contracts. For a full list of serializable types, see Types
Supported by the Data Contract Serializer.
New complex types that you create must have a data contract defined
for them to be serializable. You can explicitly create a data contract by using DataContractAttribute and DataMemberAttribute attributes.
This is normally done by applying the DataContractAttribute attribute
to the type.
You can refer to :
http://msdn.microsoft.com/en-us/library/ms733811(v=vs.110).aspxhttp://www.codeproject.com/Articles/738844/Using-WCF-Data-Contract-Known-Types-by-Example
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Problem weblogic with complex types

I have deployed a web service in weblogic 10.3. I have created it with axis, and use complex types. The problem is when I test the WS:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body>
<PruebaRequest xmlns="http://servicioweb.dispensaciones.es/">

<result>6</result>
</PruebaRequest>
</env:Body>
</env:Envelope>
Service Response
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Server CodecHandler Failed to decode
-> Failed to decode message
</faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">weblogic.wsee.codec.CodecException: Failed to decode message
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:186)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:139)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:40)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=PruebaRequest@http://servicioweb.dispensaciones.es/
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalElement(UnmarshalResult.java:226)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshalElement(UnmarshallerImpl.java:166)
at weblogic.wsee.bind.runtime.internal.LiteralDeserializerContext.unmarshalElement(LiteralDeserializerContext.java:89)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeElement(BaseDeserializerContext.java:182)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeElement(BaseDeserializerContext.java:117)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:494)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:287)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:172)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:125)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:180)
... 22 more
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=PruebaRequest@http://servicioweb.dispensaciones.es/
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalElement(UnmarshalResult.java:226)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshalElement(UnmarshallerImpl.java:166)
at weblogic.wsee.bind.runtime.internal.LiteralDeserializerContext.unmarshalElement(LiteralDeserializerContext.java:89)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeElement(BaseDeserializerContext.java:182)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeElement(BaseDeserializerContext.java:117)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:494)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:287)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:172)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:125)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:180)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:139)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:40)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Could anyone help?

It seems WLS is not comfortable with complex types in WebServices signature. In fact, it seems so for array of classes too. When I exposed a java method with a signature like:
public myClass\[] myMethod(myClass\[] param) {}
I got the same exception. However, the same WebService is working well on oc4j (embedded in jDev)
Edited by: speakingTree on Aug 17, 2009 12:57 AM

Unsupported feature: Faults with Complex types

I am confused about the statement that WebLogic currently does not support Faults
with Complex types. In a pilot project I am working on we did expose custom complex
exceptions and it appeared that WebLogic correctly created the WSDL Fault definitions.
Were we just lucky? Is the recommended approach to only use exceptions that extend
SOAPFault?
This may sound like a strange question because it appears WebLogic handled this
correctly, but the part of the project is to document possible problem areas when
exposing Web Services. If custom Faults are a problem area I need to addres it.
We are working with Weblogic 8.1, but are not using Workshop.
The web service that throws 2 custom exceptions(extend Exception); AvailabilityException
and AvailabilityQueryException
AvailabilityQueryException extends AvailabilityException and has some defined
properties (statusCode and statusText).
The fault definition in the wsdl is below?
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.cardinal.mps.availability.ejb"
elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.cardinal.mps.availability.ejb">
<xsd:element type="stns:AvailabilityException" name="AvailabilityException">
</xsd:element>
<xsd:element type="stns:AvailabilityQueryException" name="AvailabilityQueryException">
</xsd:element>
<xsd:complexType name="AvailabilityException">
</xsd:complexType>
<xsd:complexType name="AvailabilityQueryException">
<xsd:complexContent>
<xsd:extension base="stns:AvailabilityException">
     <xsd:sequence>
     <xsd:element type="xsd:string" name="message" minOccurs="1" nillable="true" maxOccurs="1">
</xsd:element>
     <xsd:element type="xsd:string" name="statusCode" minOccurs="1" nillable="true"
maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string" name="statusText" minOccurs="1" nillable="true"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>

Issues around user defined exceptions, to a large part, were resolved in WLS 8.1
SP1
(cf. http://e-docs.bea.com/wls/docs81/notes/resolved.html#1604925 ).
Also, similar issues in the wsdl-to-service approach were resolved in WLS 8.1
SP2 (cf. http://e-docs.bea.com/wls/docs81/notes/resolved.html#1546275).
If you have any specific issues please feel free to contact BEA Support.
Regards
Shridhar
"Brit" <[email protected]> wrote:
>
I am confused about the statement that WebLogic currently does not support
Faults
with Complex types. In a pilot project I am working on we did expose
custom complex
exceptions and it appeared that WebLogic correctly created the WSDL Fault
definitions.
Were we just lucky? Is the recommended approach to only use exceptions
that extend
SOAPFault?
This may sound like a strange question because it appears WebLogic handled
this
correctly, but the part of the project is to document possible problem
areas when
exposing Web Services. If custom Faults are a problem area I need to
addres it.
We are working with Weblogic 8.1, but are not using Workshop.
The web service that throws 2 custom exceptions(extend Exception); AvailabilityException
and AvailabilityQueryException
AvailabilityQueryException extends AvailabilityException and has some
defined
properties (statusCode and statusText).
The fault definition in the wsdl is below?
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.cardinal.mps.availability.ejb"
elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.cardinal.mps.availability.ejb">
<xsd:element type="stns:AvailabilityException" name="AvailabilityException">
</xsd:element>
<xsd:element type="stns:AvailabilityQueryException" name="AvailabilityQueryException">
</xsd:element>
<xsd:complexType name="AvailabilityException">
</xsd:complexType>
<xsd:complexType name="AvailabilityQueryException">
<xsd:complexContent>
<xsd:extension base="stns:AvailabilityException">
     <xsd:sequence>
     <xsd:element type="xsd:string" name="message" minOccurs="1" nillable="true"
maxOccurs="1">
</xsd:element>
     <xsd:element type="xsd:string" name="statusCode" minOccurs="1" nillable="true"
maxOccurs="1">
</xsd:element>
<xsd:element type="xsd:string" name="statusText" minOccurs="1" nillable="true"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>

While F-92 posting with T type 210 not possible (No acquisition posted)

Hi
Asset Retirement Not Possible
We have uploded legacy data in our Production server on 01.04.2010.. after that we have to sale one of them asset .
I am using T.code :- F-92 .. but i couldn't sale that and system gives me error
Posting with trans.type 210 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 210 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
Ajay
yes we are using Group Assets for income tax depreciation
when checked at AS83 no values found under taken over value for the group asset
***. aquistion val - 0
and all other values are zero
Edited by: johnrambo on Oct 4, 2010 12:09 PM
Moderator: Don't repost threads which were locked by moderator

Hi
As I said, go to AS82 and upload the Income tax values for this group asset....
Unless you do that, system wont allow you to proceed.. May be you can enter a nominal value if it is important to sell the asset now and later on correct it
Regards
Ajay M

Error : Posting with trans.type 200 not possible (No acquisition posted)

Dear All,
Iam getting error while doing asset retirement thru ABAVN. Error is mentioned below. Pls do the needful.
Posting with trans.type 200 not possible (No acquisition posted)
Message no. AA324

Dear Bird,
Already asset has been posted , but then also it shows the same error.
pls help on this.
regards
Ranjit..

Asset Retirement (ABAON) error - Posting with trans.type 210 not possible

HI All,
I was trying to sell an asset using transaction ABAON which is fully depreciated, but I am getting the error -
" Posting with trans.type 210 not possible (No acquisition posted)"
The Scenario is, there is an asset(car) which was uploaded during implimentation and it got depreciated fully in the month of april.
The same asset(car, which is fully depreciated) is sold for an amount of Rs 40000/-.
So, I was trying to post it with some revenue vlaue in transaction ABAON, but I am getting the above error.
(The Asset value was an uploaded during implimentation,it was not an acquisition value from SAP. It was an uploaded value from legacy data)
Could any one help in this, or let me know the correct process for this kind of transactions.
Awaiting for a reply.
Regards,
Upendra

HI Mamta,
Thanks for the reply.
While Uploading the data was uploaded as asset balance upload for prior year with value.
Plase let me know what do you propose, to be done for this.
Regards,

FI _AA errr Posting with trans.type 210 not possible (No acquisition posted

Asset Retirement Not Possible
Dear,
We have uploded legacy data in our Production server on 01.04.2010.. after that we have to sale one of them asset .
I am using T.code :- F-92 .. but i couldn't sale that and system gives me error
Posting with trans.type 210 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 210 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
Can anyone Help on this topic
Regards,
rambo
deleted
Moderator: Please, search SDN*

Hi Rambo
I think you are using Group Assets for income tax depreciation
If yes, have you uploaded values into Group assets from AS82? Can you please check this and revert
Regards
Ajay M

MIRO error Posting with trans.type 159 not possible (No acquisition posted)

Hi,
I have the following probem while doing MIRO. Would appreciate if someone could help.
Error in Purchase invoice posting MIRO :-
The user has created a PO for asset in FY2010 and has performed a MIGO in FY2010.
Now in FY2011 the user tries to invoice against the above asset and wants to post it thru Trans MIRO.
System gives an error during MIRO "Posting with trans.type 159 not possible (No acquisition posted)" Message no AA 324
Trans type 159 has trans type group 12 attached to it.
MIGO can not be reversed because it belongs to the closed FY.
Please help

Hi
refer notes 1526247 and 1507808... Though it relates to Japan, but the issue is same
Br, Ajay M

ASSET TRANS-Posting with trans.type Z30 not possible(No acquisition posted)

Hi Experts,
Am creating a sub asset 001 for my_asset_1, via 'BAPI_FIXEDASSET_CREATE1'. Fine.
Then, am trying to post the Asset transfer for my_asset/001 by using a BAPI of 'AMDP_BAPI_CALL_ON_TRANSACTION'.
But, am getting the Error(via ABUMN am NOT geetting any ERROR)- <i><b>Posting with trans.type Z30 not possible (No acquisition posted)</b></i>
Am passing paras, like,
so, pls. clarify that,
1 - Wht is the meaning of Error message am geeting?
2 - How to fix it?
thanq.
Message was edited by:
Srinivas
Message was edited by:
Srinivas

closing, bcoz, did not get good answer

MIRO - Posting with trans.type 159 not possible (No acquisition posted)

Hi all,
I have a case where an asset PO was created with multiple account assignment in one line item. For example, purchase 10 pc of printer with 10 asset numbers specified in the account assignment tab. By standard SAP, the GR is non-valuated.
The GR of the PO was done in the previous period. Now, when the invoice is to be posted thru MIRO. The system generate error message to me. The error message is "Posting with trans.type 159 not possible (No acquisition posted)" and message number is AA324.
The reason of this error is due to no acquisition date in the asset master. GR is non-valuated hence, the acquisition date is not populated in the asset as well. I believe this is quite a common problem. Kindly advise any workaround solution.
Thanks.
Tom

Hi
refer notes 1526247 and 1507808... Though it relates to Japan, but the issue is same
Br, Ajay M

Error posting with trans.type 159 not possible (no aquisition posted)

Hello All,
A user has created an PO for asset with GR non valuated in 2007 and has performed a MIGO/GR in the same year 2007. Now in 2008 the user has received an invoice against the said asset and wants to post it thru Trans MIRO.
At the time of posting the invoice the user gets the error "posting with trans.type 159 not possible (no aquisition posted)" . Since this is a completely new asset and GR non valuated asset process is a standard in SAP why is the system recognising the transation type as 159 i/o trans type 100 ie new asset aquisition.
If i post a dummy value to the same asset using FB01 the system accepts the value but the same process if i intend to follow usin MIRO system does not allow.
Can you guys help me
Thanks
Nelson

Thanks Paul for your reply, I checked the depreciation key. inthe key the "Aqu only allowed in capitalization year is marked as NO"
Therefore the problem is not the depreciation key
Thanks
Nelson

ABUMN: Posting with trans.type 300 not possible (No acquisition posted)

Hello everyone,
I have seen a few threads on this topic, however I am still not finding a resolution to my issue. I am very new to the FICO configuration scene and probably need a little more hand holding than the others who have asked this question.
I am having and issue using ABUMN while transfering a Capital Investment Project (CIP Asset) under a asset class of AUC, to a standard fixed asset. The CIP has been capitalized. However, when I try to perform the transfer I am receiving the following error:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
I have read through SAP NOTE 327088 (for retirements transfer variant 4) and it just doesn't help me with the issue. I know it probably should, but I do not know enough about this process in order for it to make a whole lot of sense.
If anyone can help me with this, it would be greatly appreciated. Again, I am very new, so I will probably have several follow-up questions as well.
Thanks in advance for the help!
Rhonda

Okay...
I have finally figured this out on my own.
When trying to transfer a capital investment project asset with an AuC class (asset under construction), ABUMN is not to be used.
1st. The internal order needs to be fully settled (KO02). Create a settlement rule "FUL" for the designated fixed asset.
2nd. Run "Actual Settlement" run via KO88.
This should transfer everything from the CIP asset to the fixed asset. You can double check this via the S_ALR_87011967 - ... by Plant report. Run this report prior to performing the steps above and the money will show in the CIP asset account, run it again after the above steps. The CIP should be zeroed out and the fixed asset should now carry the amount.

RPC calls to Operations with complex types is it possible?

Similar Messages

Maybe you are looking for