'Job Management' Work Center - Error in Message processing

Hi,
I'm trying to create a change request in the 'Job management workcenter, when I try to edit/view the job it throws me an error "Your are not allowed to process the message". How do I resolve this?
Thanks & Regards,
Esha Raj

Hello,
as the Job Request is a CRM message at the end (usually of transaction type SLFN or rahter SLFJ) you have to configure your assigned business partner properly (in transaction BP). Your business partner has to be configured as employee so that he is allowed to process CRM messages. It is basically the same configuration required as for the SAP Service Desk.
Best Regards
Volker

Similar Messages

Mail on success or error in message processing

Hi experts
I need to configure a scenario
1. Receive idoc from an SAP system
2. Convert the Idoc into File and Place it in the NFS File directory.
3. On success of the message, I need to mail to SAP Owner regarding the success of the message.
4. On error as well , i need the error details to the SAP Owner.
I had configued all the basic steps in IR. I had struck with the BPM part.
Please suggest with the steps in the BPM.
Thnz

hi Mohamed,
For sending the mail on success or error in message processing you need to go to the runtime workbench and configure the scenario for mail alerts.
You need to create the alert rules for the success scenario and the failure scenario.
While creating the rules you can specify the message id's to which the mail should be sent.
Please refer to the below link for more clarification.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Kindly search SDN also as there are several threads in the forum answering the same question.
Regards,
Alpa.

How to manage work center in Production order

Hi,
I am producing a material having one operation (suppose cutting), which I have mentioned in the routing. I have also mentioned the work center in routing on which cutting operation will be performed. When I make the Production order of 1000 pcs there comes only one work center. But practically, they are producing these 1000 pcs on two different work centers ( 500 on one and 500 on second). How to manage this in SAP.
Kindly help me.
Thanks and Regards,
Yogesh Singla

Dear ,
What is the individual capacacity of the Work Centre -CR02-Header -No of Individual Capacity ?
I think you must be using similar kind of work centre of 2 no 1000 pc .Now , when you are creating routing for this , you should hit Required Spilliting in Routing Operation -Select Operation line item and then Double click -Select Spilitting and enter splitting No 2.
At the same time in CR02-Work Center -Capacity Tab -Hit the Header -In the Bottom of the Detail Capacity Header -Avaialabile Capacity -Include 2 as Number of Inidvidaul Capacity and SAVE.
Now based on thr required spilittinga and invidual caapcity , it will consider the Work Centre Load .
Other wise , you can enter one more operation line in routing with similar Labor hrs , work center and control key in routung for production of 1000 pc .
Hope it clarifies
Regards
JH

CNR2-assign person to work center error: the cost center is deleted

Hi guys,
i have a problem with assigning a person to a work center using CNR2.
i select the person and i add it but when i hit SAVE i get this warning message:
"RP718: a segment could not be derived". the person will then be allocated to the work center BUT when i check in PA30 i can see that the persons cost center is DELETED :O.
could you please help me with this? i tried a lot of scenarios but i could still not find the answer.
thanks,
emi

Hi
Cost Center must be maintained for that person in HR master data. Please have your HR person look into this and maintain the data and try again. Cost center and Atype of that person would bring in actual costs (equivalent of hours) on the receiving objects when time sheet is being recorded.
Regards,
PSR

Balancing field "Profit Center" error during Payroll Processing

Hi,
Our Payroll team is processing salary however we are getting following error:
*+Balancing field "Profit Center" in line item 008 not filled
Message no. GLT2201
Diagnosis
The field Profit Center marked as balancing is not filled with any value in line item 008, even after document splitting.+*
Scenario is - we are trying to process salary of an employee who got transferred from one Cost Center to another Cost Center during the month. Entry that's being generated (however could not get posted) is:
1. SALARY-STAFF                    CC01
2. SALARY-STAFF                    CC02
3. DA-STAFF                              CC01
4. DA-STAFF                              CC02
5. OTHER ALLOWNCE-STAFF   CC01
6. OTHER ALLOWNCE-STAFF   CC02
7. T/BENEFIT PF BRD CNT          CC01
8. NET SALARY PAYABLE        -
System is splitting all the expense components however it's not able to split NET SALARY PAYABLE account.
We have checked following things:
- NET SAL.PAYABLE GL account is included in 'Classify GL Account for Doc Splitting' with Category 0100 (Balance Sheet Account)
- Document Type AB is also included in 'Classify Document Types for Doc Splitting'
- New GL is activated
- Document Splitting Characteristic for General Ledger are Profit Center (Mandatory) & Segment (Mandatory)
Could someone please advice how can we fix the issue?
Thanks,
SS

Hi,
Double click on NET SALARY PAYABLE GL account 008 line item and click on more data and give me profit center and save
Thanks,
Raviteja

Error in message processing

HI friends,
Iam facing a problem with a message which is failed at Call Adapter phase of pipeline. The error is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:TimeSent>2006-09-01T17:55:04Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SAPERP_100_X</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_SSC_USER_ROLES</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>C066A_MIIS_D</SAP:Service>
<SAP:Interface namespace="http://mbco.com/humanresources/usermanagement">UsersList_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>0fVlKrKPOra8PalZG0qABQ==</SAP:ObjectId>
<SAP:SWCV>ri/ZsDOqEduXJsPsx74ldQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://mbco.com/humanresources/usermanagement">UsersList_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>302</SAP:P1>
<SAP:P2>Moved Temporarily</SAP:P2>
<SAP:P3>Redirect</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 302 reason Moved Temporarily explanation Redirect</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2006-09-01T17:55:04Z" wasRead="false">
<SAP:Engine type="AE">af.xid.mbsdalxi50</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2006-09-01T17:55:05Z" wasRead="false">
<SAP:Engine type="IS">is.00.MBSDALXI50</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-09-01T17:55:06Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20060901</SAP:Date>
<SAP:Time>125506</SAP:Time>
<SAP:Host>MBSDALXI50</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAFUSER</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>008</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal>XBTOI___0000</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">C7BE2574084844F873FA2EE4</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>89885</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>92145</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>89885</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>85157</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PLAINHTTP</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>46</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.415</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.446</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.446</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.462</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.462</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.774</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.774</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.79</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.9</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.9</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.165</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.165</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.4</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.431</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.493</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.54</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Fatal</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>A87A357B08C7321295F803CCEC380BDC</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>SAPERP_100_X</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>C066A_MIIS_D</SAP:ToServiceName>
<SAP:ToInterfaceName>UsersList_MI</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>http://mbco.com/humanresources/usermanagement</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">C066A_MIIS_D</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP_IB_IAM_USERLIST</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">plainHTTP</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>url</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>authenticationModeBasicAnon</SAP:Name>
<SAP:Value>basicNonSAP</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>contentType</SAP:Name>
<SAP:Value>text/xml</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>copyHTTPDest</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>copyURL</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>dynConfigFailOnMissingProperties</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>enableDynConfigReceiver</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>epilog</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fifthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fifthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>firstHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>firstURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fourthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fourthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>headerFieldSelectionRcvr</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>mbsdaliam51.miller.americas.gcn.local</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value>HS37</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>maskSpecialCharacters</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>messageGuidToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/SAP/SAPUserlist.aspx?sapuserlist=</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>80</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>prolog</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>proxyHost</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>proxyPort</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>qosToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>queueIdToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>receiverInterfaceToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>secondHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>secondURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>senderPartyToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>senderServiceToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sixthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sixthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>thirdHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>thirdURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>urlParamSelectionRcvr</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>xmlEncoding</SAP:Name>
<SAP:Value>UTF-8</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external = XIParty</Trace>
<Trace level="1" type="T">Receiver agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<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=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = MBSDALXI50:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 199.190.37.116</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z 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 = 00304104E0001C91043C81C33CF04210</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 00304104E0001C91043C81C33CF04210</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0017</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0017</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 00304104E0001C91043C81C33CF04210</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z 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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - C066A_MIIS_D</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) C066A_MIIS_D UsersList_MI</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: UsersList_MI</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOI___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</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">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="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z 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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping D1F5652AB28F3AB6BC3DA9591B4A8005</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping AE2FD9B033AA11DB9726C3ECC7BE2575</Trace>
<Trace level="1" type="T">Interface Mapping http://mbco.com/humanresources/usermanagement UsersList_IM</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_UsersList_MM_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_UsersList_MM_.</Trace>
<Trace level="3" type="T">Load ae2fd9b0-33aa-11db-9726-c3ecc7be2575, http://mbco.com/humanresources/usermanagement, -1, com/sap/xi/tf/_UsersList_MM_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_UsersList_MM_.class (http://mbco.com/humanresources/usermanagement, -1) in swcv ae2fd9b0-33aa-11db-9726-c3ecc7be2575.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_UsersList_MM_ completed. (executeStep() of com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-SAPERP_100_X</Trace>
<Trace level="2" type="T">-C066A_MIIS_D</Trace>
<Trace level="2" type="T">http://mbco.com/humanresources/usermanagement.UsersList_MI</Trace>
<Trace level="2" type="T">Channel found: - C066A_MIIS_D - HTTP_IB_IAM_USERLIST</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for Plain HTTP adapter: HTTP</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = PLAINHTTP</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_HTTP_PLAIN_OUTBOUND</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type=

Hi
According to following link (about HTTP error 302), you have maybe a problem with the user/pwd with your HTTP adapter.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
Else search inside OSS notes with "HTTP error 302" and/or "ATTRIBUTE_SERVER"
Mickael.
No access to service marketplace, for the moment.

Errors in message processing

if in atypical case 100 files have been sent to the receiver side and later it is found that 10 files had errors, how to identify the names of the files which had errors .

The error you mean the some busniess error right?
these are the steps with which you can get the filename alone
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i - Dynamic File Name Part 1
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii - Dynamic File Name Part 2
so what you have to do it check the logic in the mapping which detemines the erorr busniess in your strucutre which hold the error mesage add the filed filename and pass the filename to this strucutre....
i think this should work...

In the Graphic Tab and Work Center Error The Page Cannot be displayed

Hi In the Solar01 and also in the Solman_Workcenter I am getting error "The Page Cannot be displayed"
In the Solar01 - I have Business Processes save and under the Graphic Tab when I am clicking on the correct Business Scenario Node. I am expected Graph to display. But Showing error
In the Solman_Workcenter - I set up the added the Starndard Role Busing Solaman Basic Role and + implementation role. When i go under Solman_workcenter transaction I am getting the same prolbem i.e "The Page Cannot be displayed"
Any Idea friends.
Appreciate your help
-Santh

Hi,
Refer note 834832. Check activation of services in transaction SICF and the patch level of your SAP GUI.
Thanks.
Kathir

Job Management

Hello SolMan users !
I am playing around with the new Work Centers, and what I'd like to setup first is the Job Management Work Center.
Currently, when I open this work center, in the Overview, I have all the sections (Job Requests, Job Monitoring, ...), but no numbers are displayed, there are '???' everywhere.
Also, I have activated the WebDynpro services for Job management. I tried scheduling a job in a remote system with the BC-XBP scheduler, but I got a "No connexion to BC-XBP" error message.
I am totally at a loss about what I need to setup to have this working, and I cannot find any documentation.
Could someone point out to me what I am missing ? What is BC-XBP ? Is it something that needs to be configured in SolMan/the remote systems ?
Finally, is there any documentation about Work Centers customizing ?
Thank you.
Thomas

Hello,
please begin with reading SAP Note 1122497 - Process Scheduling for SAP Solution Manager.
The Application Area for this case is "SV-SMG-PSM".
You have to install the add on SAP CPS by Redwood. It is a part of license of SAP Netweaver.
The add on component is ST-PSM.
Best regards
Thomas Hiesener

Please help me regarding VAR customer create new message in work center

Hi, guru
I have encountered with a problem regarding, for example, when VAR customer 'X' create new message in work center and specify message processor to partner no '1' (partner no 1 has employee role with username 'A' in BP) but when username 'A' log on and open work center via SAPGUI to find a new message created to him, username 'A' did't got a new message from VAR customer 'X' whom choose specify message processor to him and work center show My Messages (0)
why, do I set something config wrong ?
Any recommend would be appreciated
thank you very much

Hi
1) can you check in CRM_DNO_MONITOR and oepn the ticket , whethere the processor name appearing in the ticket?
2) Does your customer assign the processor manually or any automatic support team assgnemt, if so please verify your automatic support tean assignment against the blog
[/people/dolores.correa/blog/2007/10/06/service-desk-support-team-determination|/people/dolores.correa/blog/2007/10/06/service-desk-support-team-determination]
3)Might be an authoraisation issue of the Processor. assign SAP_ALL access and check again
[Service desk roles|http://help.sap.com/saphelp_sm32/helpdata/en/0a/f12c41ab78f66fe10000000a1550b0/content.htm]
Thanks,
Jansi

Message processing failed: Invalid http response: 220

Hi Experts,
I am working on FILE to SOAP scenerio. File is coming in XI properly. But in the SOAP CC its showing this error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530 : java.io.IOException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530
Any ideas ?
-=Soniy

Hi Sonia,
Please go throgh the following links for use ofr XML SPY
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
Re: Stand alone testing using XML Spy
WSDL frm Altova xml spy
Invoke Webservices using SAPXI
Testing XI exposed Web-Services
Regards
Sridhar Goli

Cannot open Catalog Manager and Job Manager on Windows 7 (11.1.1.6.2 BP1)

Hi,
We recently upgraded to OBIEE version 11.1.1.6.2 BP1 and installed Client tools from the same version (downloaded from Oracle Support). Once installed, ODBC connections are created to connect to the BI Server and we are able to connect to BI Server using Administration Tool. But Catalog Manager and Job Manager are not opening.
Is there any setup missing to make Catalog Manager and Job Manager work?
Thanks in advance.

Hi,
It is a known bug. Please find the solution here.
http://123obi.com/2013/02/unable-to-open-catalog-manager-obiee-11g/
Cheers,
Kalyan Chukkapalli
http://123obi.com

Change Work Center during production order confirmation

Dear All,
I must to modeling this situation:
I created an production order. In routing I used an work center A.
After I confirmed a half of quantity, the work center A was damaged and I must to change it, with the work center B.
The system allow this change, but when I checked the costing, the situation isn't real. The system counted the costs just for the work center A, and no for work center B.
My question is: it's possible to change the work center, during production order confirmation and the costs updated with new cost?
Thank you for your answer!
Regards,
Marian

once a Order is released, the Process order detaisl for that order is frozen.
however if you want to do it, change the order status to CRTD after reversing the Movements done.
Do READ MAster data , this will copy the new Work center , redo the previously done Moevements.
if the change is long term.
or
Just manually add the new work center and do the processing. if the change is temporary.

AS2 adapter error during inbound processing

Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
Marco

Hi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

Quality inpsection on Work center (with/without Material Ref.)

Dear All,
I have scenario, where I have to do the in process inspection on machine (work center) to measure various process parameters that has a direct link with product quality. it is basicallly with out material reference.
I tried using in process inspection for production order but there are several constraints due to which It will not work for certain cases. if we record the readings on each interval against machine/workcenter then every thing will be fine.
how can we do it in SAP.
thanks
MD

Yes its a variant product (Like aluminium sheets rolls for different gauge and widths). which means alot of different product variants produce on same machine with same machine parameters.
so for inspection, product has secondary importance, we want to study the machine parameters to monitor which should remain same over the time and product.
Further at the end, the report we want to see is based on machine not product.
thx

'Job Management' Work Center - Error in Message processing

Similar Messages

Maybe you are looking for