Problem Accessing Protocol Classes in INBOUND PROXY
Hi guys.
Im having problems accessing Protocol Classes in a inbound proxy.
I have this code that is copied from:
http://help.sap.com/saphelp_nw04/helpdata/en/a7/3b2a2d45a34a23b75e3b18745c63bc/frameset.htm
DATA: lo_server_context TYPE REF TO if_ws_server_context,
lo_payload_protocol TYPE REF TO if_wsprotocol_payload.
lo_server_context = cl_proxy_access=>get_server_context( ).
lo_payload_protocol =
lo_server_context->get_protocol( if_wsprotocol=>payload ).
But Im getting this error:
The result type of the function method cannot be converted into the type lo_payload_protocol
If I try to get the attachment protocol with this code:
DATA: lo_server_context TYPE REF TO if_ws_server_context,
lo_attachment_prtcl TYPE REF TO IF_WSPROTOCOL_ATTACHMENTS.
lo_server_context = cl_proxy_access=>get_server_context( ).
lo_attachment_prtcl = lo_server_context->get_protocol( if_wsprotocol=>ATTACHMENTS ).
Im getting the same error.
What am I doing wrong? It' s code copied fror SAP Library!!!
Thanks a lot.
hi,
you are choosing wrong type for lo_payload_protocol.
you must change like this
lo_payload_protocol TYPE REF TO IF_WSPROTOCOL.
regards,
orhan
Similar Messages
-
Please Help!!! Problems access other classes methods
I am having a problem accessing another classes methods varibles. I have tried a number of ways but with no success. Here is my problem:
I have the main(), from there it's calls the class GetVar(), GetVar stores info in Class HousingForVar(), and finially, I have a class TryinToTalkToHousing() that I use to access HousingForVar()'s methods. I know I can use the keyword new but if I do that then it erases over the data I put in. Please can anyone help, this has been driving me nutz all day. Thank you in advance.
Roman03
***EACH CLASS IS A DIFFERENT FILE****
public class TestMain
public static void main( String args[] )
GetVar getVarible = new GetVar();
getVarible.heroF();
import java.util.Scanner;
public class GetVar
public void heroF()
String someEntered;
Scanner input = new Scanner( System.in);
System.out.println("Enter a string: ");
someEntered = input.next();
HousingForVar houseForData = new HousingForVar(someEntered);
System.out.printf("Retieved from Class GetVar, you entered: %s\n", houseForData.getCollectVar() );
import java.util.Scanner;
public class HousingForVar
private String getData;
public HousingForVar(String enterInfo)
getData = enterInfo;
public void setGetVar(String enterInfo)
getData = enterInfo;
public String getCollectVar()
return getData;
import java.util.Scanner;
public class TryinToTalkToHousing
public void someMeth()
String getInfoFromHousing;
System.out.printf("Started out at TryinToTalkToHousing Class\n Retieved from Class GetVar from %s\n",
houseForData.getCollectVar() );
\* I know this doesn't work, but if I make a new object of the class HousingForVar it's going to write over my input, so what do I do? I am still learning, Please help*\I don't use 1.5, so you'll have to convert it back, but see if you can follow the flow of this
import java.io.*;
class TestMain
GetVar getVarible;
public TestMain()
getVarible = new GetVar();
getVarible.heroF();
System.out.println("******");
new TryinToTalkToHousing(this).someMeth();
public static void main(String[] args){new TestMain();}
class GetVar
HousingForVar houseForData;
public void heroF()
try
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
System.out.print("Enter a string: ");
String someEntered = br.readLine();
houseForData = new HousingForVar(someEntered);
System.out.println("Retieved from Class GetVar, you entered: "+houseForData.getCollectVar()+"\n");
catch(Exception e){e.printStackTrace();}
class HousingForVar
private String getData;
public HousingForVar(String enterInfo)
getData = enterInfo;
public void setGetVar(String enterInfo)
getData = enterInfo;
public String getCollectVar()
return getData;
class TryinToTalkToHousing
TestMain parent;
public TryinToTalkToHousing(TestMain t){parent = t;}
public void someMeth()
System.out.println("Started out at TryinToTalkToHousing Class\n"+
"Retieved from Class GetVar, you entered: "+parent.getVarible.houseForData.getCollectVar()+"\n");
} -
Problems accessing JavaBeans classes in a JSP.
Hi,
I have created some Javabeans �Product� and �ShoppingBasket� and compiled into their classes ok.
I have created a JSP that uses these beans, however when I do a web run from Jbuilder4 I get a message saying it is unable to compile the class.
I don�t understand as the classes are already compiled. I double checked the spelling and the made sure the classes were in the same folder.
Is this some problem with Jbuilder 4 or the way I have imported the classes?
Here is my import statement:
<%@ page language="java" contentType="text/html" import="ShoppingBasket, Product, java.sql.*" %>
and here is the error message Jbuilder is giving me:
org.apache.jasper.JasperException: Unable to compile class for JSPC:\OU2007\TM427\EasyShop\work\localhost_8080\_0002fmyproject_0002feasyshop_0002fshopproducts_0002ejspshopproducts_jsp_0.java:15: Class ShoppingBasket not found in import.
import ShoppingBasket;Cross post:
http://forum.java.sun.com/thread.jspa?threadID=5149952
MeTitus -
Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1
I am trying to build a component which has the ability to instantiate and execute
an known EJB method on the fly.
I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
I know that the EJB I am trying to invoke is deployed and available on the server,
as I can see it in the console, I also seen to have been able to get the remote
interface of the object, my problem occurs when I try and access the class object
so I can perform a create on the object and then execute my method
The code I have written is below:
private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
throws Exception {
String homeCreate = "create";
Class []homeCreateParam = { };
Object []homeCreateParamValues = {};
try {
//This call seems to work and doesn't throw an exception
Object home = pCtx.lookup(pJNDIName);
//However this call throws a java.lang.ClassNotFoundException
Class homeBean = Class.forName(pHomeBean);
Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
} catch (NamingException ne) {
logStandardErrorMessage("The client was unable to lookup the EJBHome.
Please make sure ");
logStandardErrorMessage("that you have deployed the ejb with the JNDI
name "+pJNDIName+" on the WebLogic server ");
throw ne;
} catch (Exception e) {
logStandardErrorMessage(e.toString());
throw e;
Any advice would be really appreciated, I'm fast running out of ideas, I suspect
it has something to do with the class loader but I'm not sure how to resolve it
Regards
Jo CorlessHello Joanne,
Congratulations! I'm very happy that you've managed to fix your problem. It's
always essential to understand how to package applications when deploying on BEA
WebLogic. Usually, by throwing everything into an EAR file solves just about all
the class loader problems. :-) Let us know if you have any further problems that
we can assist you with.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Joanne Corless" <[email protected]> wrote:
>
>
I've fixed it!!!!!!!!
Thanks to everyone who gave me help!!!!
The class loader was the culprit which is what I suspected all along.
As soon
as I put the 2 jar files I was using into an EAR file the problem went
away!!!!!
Thanks again
Jo Corless
"Ryan LeCompte" <[email protected]> wrote:
Hello Joanne,
As Mr. Woollen mentioned, I also believe it's a problem with the class
loader.
You need to be careful how you arrange your EJBs, because WebLogic has
a specific
method in which it loads classes in an EAR, JAR, and WAR file(s). Please
refer
to http://dev2dev.bea.com/articles/musser.jsp for more information about
BEA WebLogic
class loading mechanisms and caveats. Also, try printing out the various
methods
that are available on the object that was returned to you via reflection.
For
example, use the getMethods() method, which returns an array of Method
objects
that you can subsequently cycle through and print out the various method
names.
This way you can discover if the class found/returned to you is indeed
the one
you intend to locate.
Hope this helps,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Rob Woollen <[email protected]> wrote:
I believe the issue is the home interface class for this EJB is not
available in the class loader which is doing the reflection.
If you do:
getClass().getClassLoader().loadClass(homeInterfaceClassName)
I suspect it will fail. Reflection still requires that the class be
loadable.
-- Rob
Joanne Corless wrote:
Hi Slava,
If I make my code look like you describe below I get a compliationerror telling
me that
home.getMethod() is not recognised (no such method)
If I change it slightly and use
Method homeCreateMethod =
home.getClass().getMethod(homeCreate,homeCreateParam);
The code will compile OK but when executed it still throws a NoSuchMethodException
Any ideas ?
Thanks for your help so far
Regards
Jo Corless
Your code should look like
Object home = pCtx.lookup(pJNDIName);
Method homeCreateMethod =
home.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
Regards,
Slava Imeshev
"Joanne Corless" <[email protected]> wrote in message
news:[email protected]...
Hi Ryan,
I also wanted to mention that if you do a "header search" in this
particular
newsgroup
with the search query as "reflection", you will see many previousmessages
regarding
reflection and EJBs. I believe you could learn a lot from thedifficulties
that
others have faced and solved.I tried that and although there was a number of similar cases noneof them
actually
seem to fix my issue. Thanks for the suggestion though
Are the EJBs that you are trying to access accessible via your
system
classpath?
Try to avoid having them accessible via the main system classpath,and
only bundle
them in your appropriate EJB jar files (contained in an EAR file,for
example).Maybe I should have laid the problem out a little clearer.
I have a number of EJB's bundled up in a JAR file which is hot deployedto
the
server. Within this first JAR file is an EJB (SSB) component that
needs
to
be
able to invoke a known method on another EJB. This second EJB may
or
may
not be
within the first JAR file but it also will be hot deployed.
The component trying to invoke the method on the 2nd EJB has to
be
able to
create
an instance of the 2nd EJB without actually knowing anything bar
a
JNDI
Name which
is passed in at runtime.
I can get as far as doing the
Object home = pCtx.lookup(pJNDIName);
This returned a class with the name
"com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
Impl_WLStub"
My problem seems to occur when I try and invoke the create method
Method homeCreate = home.getClass().getMethod("create", new Class[0]);
My code throws a java.lang.NoSuchMethodException at this point so
I
am
unable
to progress to the next step of :
Object bean = homeCreate.invoke(home, null);
So I can return the instantiated bean back to the calling client.
Why am I getting the NoSuchMethodException, is is because I am gettinga
stub
back rather than the home interface and if so how do I get the truehome
interface
from the bean
Thanks in advance
Jo Corless -
Generated Class is not called by Inbound Proxy
Uploading data to Ztable of ECC by using inbound proxy.
The messages are tranfered to SAP ECC from SAP XI.
Monitoring in SXMB_MONI in SAP XI DEV can see Success flag
Monitoring in SXMB_MONI in SAP ECC can see inbound message stored in QUEUES only.
I configured the Application Integration Engine as per the help document.
In Reciever XI Adapter set the addressing type URL.
Coding is correct in the method of the generated class.
Let me know if any configurations yet to be done.
Let me know how to proceed furthur.
ThankYou in Advance.hi
Go to SMQR of the ECC and register and activate the queues again.
Also ensure that u are implementing the correct methods of the proxy
EXECUTE-SYNCHRONOUS / EXECUTE-ASYNCHRONOUS
rgds
Arun -
Problem accessing another public ip in same subnet
Hi,
I have searched around for a previous post regarding this but can't find an issue similar to mine (or I'm just too stupid to understand that it is )
I have a Cisco 5505 at a small business that I help. The problem is that the ISP are providing public IPs to multiple customers in a /24 subnet. The ASA has a single public IP configured 8.8.8.8 (not really, just for the examples sake) with a subnet mask of 255.255.255.0.
The webserver I have to access is not managed by me and is located in a different location (same town though) has 8.8.8.115, it is located in the same subnet as the ASA.
How would I make this work? I have tried to configure a static arp entry for the web server but it just won't work. If i place a computer directly on the outside interface I have no problem accessing the web server.
I am running ASA version 8.2, but I could upgrade if it would help me solve the problem.
Any help with this issue is much appreciated.The ISP only specify one gateway in that range and that is 8.8.8.1 so any other would not let me access internet.
Once again thank you for your time.
: Saved
ASA Version 8.2(1)
hostname ciscoasa
domain-name XXXXXXX
enable password XXXXXXX encrypted
passwd XXXXXXX encrypted
names
name 8.8.8.8 Outside_IP
name 192.168.20.2 Server
name 192.168.20.11 rav-dc01
name 192.168.20.12 rav-ms01
name 192.168.20.13 rav-rds01
interface Vlan1
nameif inside
security-level 100
ip address 192.168.20.1 255.255.255.0
interface Vlan2
nameif outside
security-level 0
ip address Outside_IP 255.255.255.0
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
boot system disk0:/asa821-k8.bin
ftp mode passive
dns server-group DefaultDNS
domain-name XXXXXXX
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object-group protocol TCPUDP
protocol-object udp
protocol-object tcp
access-list inside_nat0_outbound extended permit ip any 192.168.25.0 255.255.255.0
access-list RemoteVPNSplittunnel standard permit 192.168.20.0 255.255.255.0
access-list outside_access_in extended permit tcp host 100.100.100.228 interface outside eq 3389
access-list outside_access_in extended permit tcp any interface outside eq smtp
access-list outside_access_in extended permit udp any interface outside eq 4125
access-list outside_access_in extended permit tcp any interface outside eq 4125
access-list outside_access_in extended permit tcp any interface outside eq https
access-list outside_access_in extended permit tcp any interface outside eq pptp
access-list outside_access_in extended permit tcp any interface outside eq 444
access-list outside_access_in extended permit gre any interface outside
access-list outside_access_in extended permit udp any interface outside eq 444
access-list outside_access_in extended permit tcp any interface outside eq www
access-list inside_access_in extended permit tcp host rav-ms01 any eq smtp
access-list inside_access_in extended deny tcp any any eq smtp
access-list inside_access_in extended permit ip any any
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
ip local pool RemoteVPNPool 192.168.25.100-192.168.25.200 mask 255.255.255.0
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-621.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) udp interface 4125 Server 4125 netmask 255.255.255.255
static (inside,outside) tcp interface 4125 Server 4125 netmask 255.255.255.255
static (inside,outside) tcp interface https rav-ms01 https netmask 255.255.255.255 dns
static (inside,outside) tcp interface pptp Server pptp netmask 255.255.255.255
static (inside,outside) tcp interface 3389 rav-rds01 3389 netmask 255.255.255.255 dns
static (inside,outside) tcp interface smtp rav-ms01 smtp netmask 255.255.255.255
static (inside,outside) udp interface 444 Server 444 netmask 255.255.255.255
static (inside,outside) tcp interface 444 Server 444 netmask 255.255.255.255
static (inside,outside) tcp interface www Server www netmask 255.255.255.255 dns
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 8.8.8.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
aaa-server rav_Intern protocol radius
aaa-server rav_Intern (inside) host rav-dc01
key CiscoAsa5505RAV2012
radius-common-pw CiscoAsa5505RAV2012
http server enable 8080
http 192.168.20.0 255.255.255.0 inside
http 192.168.25.0 255.255.255.0 inside
http 100.100.101.128 255.255.255.192 outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
sysopt connection timewait
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map outside_dyn_map 20 set pfs
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-SHA
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption aes-256
hash sha
group 2
lifetime 86400
telnet 192.168.20.0 255.255.255.0 inside
telnet timeout 5
ssh 192.168.20.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
management-access inside
dhcpd auto_config outside
dhcpd address 192.168.20.190-192.168.20.200 inside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ntp server rav-dc01 source inside
webvpn
group-policy RemoteVPN internal
group-policy RemoteVPN attributes
wins-server value 192.168.20.11
dns-server value 192.168.20.11
vpn-tunnel-protocol IPSec
split-tunnel-policy tunnelspecified
split-tunnel-network-list value RemoteVPNSplittunnel
default-domain value rav.nu
split-dns value rav.nu
username SupportVPN password XXXXXXX encrypted privilege 0
username SupportVPN attributes
vpn-group-policy RemoteVPN
tunnel-group RemoteVPN type remote-access
tunnel-group RemoteVPN general-attributes
address-pool RemoteVPNPool
authentication-server-group rav_Intern
accounting-server-group rav_Intern
default-group-policy RemoteVPN
tunnel-group RemoteVPN ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map global_policy
class inspection_default
inspect pptp
inspect icmp
inspect icmp error
service-policy global_policy global
prompt hostname context
Cryptochecksum:8481ab3aa01b23bad17bacb2aca7197a
: end
asdm image disk0:/asdm-621.bin
no asdm history enable -
Inbound Proxy Error - JDBC to PROXY Scenario
Hi experts,
I am getting the following error while activating Inbound Proxy.
Error when creating service node. [unknown]You are not authorized to use function Netzwerkadministration
Exception of class CX_SRT_WSP_ICF
Regards,
SudheerHi Experts,
Thank you for your replys.....Problem got solved......:)
Some authorisation was missing...Now it was fine and I can activate Inbound proxy......:)
Once again Thank you for your replys.....:)
Regards,
Sudheer -
Call transaction in ABAP Inbound proxy
Hi All,
I am processing transaction KKPAN in inbound proxy. As per my knowledge, there is no BAPI or other way of processing this transaction. I have recorded a BDC, and I am calling this BDC using Call Transaction in my Inbound proxy.
The problem is, control never returns back to the proxy after I call this BDC using Call Transaction. However, interestingly, If there is an error in BDC, the control comes back to the proxy. Any ideas, why it does not successfully update data using BDC in inbound proxy?
Your inputs are appreciated.
Thanks,
NavdeepThanks for you response Akshay !
However, It didn't solve my problem. In my case, the inbound proxy class is being called successfully. The problem comes, when I use Call Transaction in the class. The call transaction works and returns error message, if there is some error in the processing; however, for when there is no error in the BDC data, the control never comes back after call transaction.
However, if I use SPROXY to test this interface, by copying the payload of the message and using the same user (As in Comm Channel), I am able to call Call Transaction without any problem. The data gets created successfully.
Now this is getting really tricky.
Still looking for ideas
Regards,
Navdeep
Message was edited by:
Navdeep Singla -
Urgent: Error in Inbound Proxy in SCM system
Hi All
Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
Thanks a lot for your help guys.
I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
Please find the XML message from ERROR node from Inbound Proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find contents of Trace XML message from Inbound proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T01:31:18Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 48165647672B03B5E10080000A0C640C</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ReplenishmentOrderNotification_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T16:19:34Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T20:52:28Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:34:19Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:35:19Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:41:24Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:07:18Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:30:07Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:53:39Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T01:04:22Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
Regards
AmolHi All
Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error. Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
Hope to hear from you soon. Thanks a lot for your inputs.
ReplenishmentOrderNotificationFault
Proxy Class (Generated)
Detailed Information
Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
Start generic process type determination 000(/SCMB/BIF_CU)
Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
Start action determination for addresses 070(/SCMB/BIF_CU)
No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
End of action determination for addresses 071(/SCMB/BIF_CU)
Start partner role determination 060(/SCMB/BIF_CU)
Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
Partner role determination completed successfully 061(/SCMB/BIF_CU)
TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
Start: read ODM order 250(/SCMB/ORDER)
End: read ODM order 251(/SCMB/ORDER)
Start: validation framework 254(/SCMB/ORDER)
Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
End: validation framework 255(/SCMB/ORDER)
Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
Start: write ODM order 252(/SCMB/ORDER)
End: write ODM order 253(/SCMB/ORDER)
BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER) -
ABAP Inbound Proxy Error !
Hi ,
I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack> <SAP:Retry>M</SAP:Retry>
</SAP:Error>
Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause ApplicationHi attached trace, kindly update wat could be the problem in case of EBP SUS Vendor replication
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:21Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = DD128437FD4A75F193690017A4F3435A</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:24Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
- <!-- ************************************
-->
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o97" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o97">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o96" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o96">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
*<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 00000008 does not exist; check entries Programm:* CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace> -
Hi
I have SRM Scenario were I am sending a Z_CREAMAS_SUSMM IDOC from ECC 6.0 to SRM 5.5 SUS via PI 7.0 . There are no errors on the XI side and the sxmb_moni of the SRM side .The message shows a successful flag on the XI as well as the SRM side . But however the functionality of the idoc does not work ie the vendor is not created in SRM SUS.
When we try to test the inbound proxy from sproxy by copying the payload from sxmb_moni of SRM and then testing it we get a short dump with the following contents .
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "SET_METHOD" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
"CL_PROXY_INBOUND_ADAPTER======CP" or "CL_PROXY_INBOUND_ADAPTER======CM00I"
"SET_METHOD"
Can any one please tell me what the error could be .
regards
Nilesh TaunkHi,
You program raise an exception as''CX_SY_REF_IS_INITIAL'.
this is due to null value passing to the object.
i hope, u r using intialization event in the custom ABAP code.
please try to change it.
warm regards
mahesh. -
Cannot access server in HQ through proxy server
Hi Experts,
We have a TMG 2010 installed and clients are accessing Internet through it.
And now there is an access problem to the destinatined server in HQ in another country, and it was fine to reach the destinated server before the servere changed its IP.
When trying to accesss the destinated server with new IP, the TMG log and report shows the connection status with
12030: The connection with the server was terminated abnoramlly.
While there is another guest segment that allows Internet access without proxy server, and they are able to access the server with no problem at all.
When I captured packets using Wireshark from the pc and found that the connection was actually from the pc to proxy server with the following result:
from PC to Proxy server
CONNECT xxx.xxx.com:443 HTTP/1.0
from Proxy server to PC
HTTP/1.1 502 Proxy Error (The connection with the server was terminated abnormally) (text/html)
Would there be a configuration problem inside TMG?
When i include the domain in https inspection exemption list, is that means client would be able to reach ther destination without being inspected?
Then how about the incoming connection? Is there any rules which will restrict HTTPS inbound?
Apart from above problem, clients also not able access some of https website such as banking with CA's, and no problem using guest segment (not through proxy server).
Thanks in advance
BenHi,
>>And now there is an access problem to the destinatined server in HQ in another country, and it was fine to reach the destinated server before the servere changed its IP.
Have you tried to re-create the rule to access the destinatined server after it changed the IP?
>>When i include the domain in https inspection exemption list, is that means client would be able to reach ther destination without being inspected?
When a site is added to the HTTPS inspection exclusion list, Forefront TMG does not check the site’s certificate for expiration or revocation. However, name mismatch and trust are always checked, unless the “No Validation” mark is set.
Reference:Troubleshooting HTTPS inspection
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
How to access a class file outside the package?
created a two java files Counter.java and TestCounter.java as shown below:
public class Counter
public void print()
System.out.println("counter");
package foo;
public class TestCounter
public static void main(String args[])
Counter c = new Counter();
c.print();
Both these files are stored under "D:\Test". I first compiled Counter.java and got Counter.class which resides in folder "D:\Test"
when i compile TestCounter.java i got the following error message:
D:\Test>javac -classpath "d:\Test" -d "d:\Test" TestCounter.java
TestCounter.java:6: cannot find symbol
symbol : class Counter
location: class foo.TestCounter
Counter c = new Counter();
^
TestCounter.java:6: cannot find symbol
symbol : class Counter
location: class foo.TestCounter
Counter c = new Counter();
^
2 errors
what could be the problem. Is it possible to access a class file outside the package?ya that's fine..if we have two java files where both resides in the same package works fine or two java files which donot have a package statement also works fine. But my doubt is, i have a Counter.class which does not reside in a package and i have a TestCounter.class which resides in a package "foo", in such a scenario, how do i tell to the compiler that "Counter.class resides in such a path, please look at that and give me TestCounter.class". i cannot use import statement to import Counter.class in TestCounter.java because i donot have a package for Counter.java.
-
How can I access another class in a MembershipRule's Expression
Hello,
I want to create an InstanceGroup using Module Microsoft.SystemCenter.GroupPopulator.
I need to collect all Logical Disks which contain an MS SQL DB Log File.
I would start as follows:
<DataSource ID="DS" TypeID="SC!Microsoft.SystemCenter.GroupPopulator">
<RuleId>$MPElement$</RuleId>
<GroupInstanceId>$Target/Id$</GroupInstanceId>
<MembershipRules>
<MembershipRule>
<MonitoringClass>$MPElement[Name="Windows!Microsoft.Windows.LogicalDisk"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MSIL!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<Expression>
<And>
<!--
First Expression
-->
<Expression>
<SimpleExpression>
<ValueExpression>
<Property>$MPElement[Name="Windows!Microsoft.Windows.LogicalDevice"]/Name$</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<!--
How can I access another class's properties ?
-->
<GenericProperty>$MPElement[Name="SQL!Microsoft.SQLServer.2008.DBLogFile"]/Drive$</GenericProperty>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<HostProperty>
<MonitoringClass>$MPElement[Name="Windows!Microsoft.Windows.Computer"]</MonitoringClass>
<Property>PrincipalName</Property>
</HostProperty>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<GenericProperty>$MPElement[Name="SQL!Microsoft.SQLServer.2008.DBLogFile"]/Drive$</GenericProperty>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</MembershipRule>
</MembershipRules>
</DataSource>
In the first expression you "see" my question:
I want to compare the LogicalDisk's Name Property with the DB Log File's Drive property.
But how can I access the DB Log File's Drive property in this MembershipRule ?
Furthermore LogicalDisk and DB Log File must be hosted on the same Windows Computer.
Would be great if somebody could help.
Thanks
SebastianHi Niki,
thanks for the idea, but that will not work. $Target/Id$ refers always to the group to be discovered.
On last week end I was given following idea, hope it will work:
Step 1
Collect all the DB SQL Logfile Objects and write computername (PrincipalName?) and Driveletter into a textfile, line by line. Shouldn't be a problem, PowerShell is your friend.
Step 2
Read the file from Step 1, build discovery data for each disk drive as object of class "Logical Disk (Server)",
and then discover the containment-relationships from those Logical Drive(Server) Objects to the InstanceGroup.
Perhaps I must do it for the OS-Version related Disks, because I need the target classes of the Logical Disk Freespace monitors. Some more work. "Risks": I donot know the discovery algorithm for the Logical Disk(Server) Objects, but a "deep
dive" into the MPs should help.
Thanks to all, who have read.
I will inform you about progress and success
sebastian -
Issue while inserting a BDC program in Inbound Proxy.JDBC-- PI-- SAP.
The scenerio is jdbcsender-sappi-inboundproxy(ECC6.0).
The issue is related to SAP Plant Maintenance Module where We have a requirement for creating Maintenance item
programmatically from (SQLDatabase)Legacy Data for one of the interface.
since there are no standard BAPIS/Idocs or function modules available from SAP side for creating the maintenance item. So I
have written BDC program and with the help of submit statement in inbound proxy program, I am calling BDC program for
creation of the maintenance item.
When I tested the program independently on proxy side the Maintenance Item is getting created successfully but when I
executed from end-to-end ie. SQLDATABASE->SAP PI-->SAP. The message is getting strucked into the queue and queue got stopped on SAP.
ECC side and the status of the message is scheduled state on SXMB_MONI transaction of SAP ECC.
As the message is in scheduled state multiple number of Maintenance Items are getting created with the same values.
Has any one of our SAP friends, encountered this type of issue while inserting a BDC program in inbound proxy, please help
in fixing this issue. FYI... I am using sap pi7.0 with service pack 24 and ecc6.0
Waiting for your kind expert guidance...
cheers,
RamRaj,
Thanks for the reply. I have tried registering the queues but still the same problem. the message got stuck in the queue of ECC and showing below message in queue.
function module StatusText
SXMS_ASYNC_EXEC connection closed (no data)
I have checked in the forums especially for this issue but no one has provided the answer for this.
Thanks and Regards
Ram
Maybe you are looking for
-
Update ActiveX References Error
There MUST be a simple way to update ActiveX References when a third party library has been updated to a new version. I had made up several VI's that passed the ActiveX Class Refnum around. This refnum was generated by right-clicking on a standard A
-
Display issue - My macbook pro 2011 detects my display but does not display an image
Hi, I am having a problem connecting my MacBook Pro (2011) to my HP 2511x display. I used the display all morning with my mbp connected and closed. When I came back, after the computer went to sleep, I cannot get any image on the display. The comp
-
Keyword problems when editing with CS6
In LR 4.2 and 4.3, when I edit with photoshop and use lightroom corrections, LR creates a new file. I edit it in CS6 and save and close. Back in LR, the file is there, the proper keywords are highlighted and there, but LR cannot find that file. In
-
My email on my wifes phone?
Let me start by saying my wife and i both have 3gs phones and SHARE an itune account. So, i either log in with my email or hers depending on whos phone is getting synced. Now for my question..........I just went on to my wifes phone to update her app
-
BI scheduler problem (AIX)
hi! I've got a problem with configuring BI Scheduler. I followed the instructions, and it all seems fine, I can start the service, I can configure iBots, I can save them, they are in the database... but when I try to run one, it gives me this error m