Waitnig status in a pipeline step

Hi guys...
I've a scenario JDBC --> XI --> JDBC, I checked the objects in the Integration Repository and are activated, I configure twice the object in the Integration Directory and when the scenario is running, some message are stuck in the pipeline step "Message Branch According to Receiver List". I look for the trace in the message step and it show the following information:
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface mi_oa_rclTec_DMS*</Trace>
<Trace level="1" type="T">select interface namespace urn:dms-grt:DMS_GRT_01</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 *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--<b>no sender or receiver interface definition found</b></Trace>
But the problem is not persistent, sometimes its works, but sometimes dont, that is, get stuck in that step.
Any ideas???
Hector

Hi Hector -
Is this all you see? What's the message status - any error? This part of the trace is not indicative of what the problem is. For example, on a standard successful message that processes all the way through, I can see exactly what you posted - it's just part of the preliminary processing. You mentioned the message reached the pipeline step "pipeline step "Message Branch According to Receiver List". So it was able to perform Receiver and Interface Determination up to this point.
Maybe you can raise the trace level to 3 to see if you get any more info - SXMB_ADM then Integration Engine Configuration->Change Specific Configuration, then:
RUNTIME (Category), TRACE_LEVEL (Parameter), 3 (Current Value)
Regards,
Jin

Similar Messages

File to Idoc Scenario -- No Pipeline steps in Moni

Hi,
I have created a File2Idoc scenario. I have done all the configurations & finally dropped the file in source directory. File got picked up and deleted from source directory, But I could see in Moni only for the Inbound message but not able to see the message mapping and Receiver determination pipeline steps in Moni.
Also viewed the communication channel for sender and it is working perfectly and it shows the logs with the details of File deleted.
Note: The XI server is newly installed and configured and this is the first scenario being executed in the server. So should there be any other installation configuration to be done, to process the file in IS.
Because as per our assumption, the file has not reached the IS and it still stays in the queue with only the Inbound message.
Regards,
Nithiyanandam

Hi Nithiyanandam,
as u described your problem i want to guide u through foll steps:
1. in xi monitor on pipeline window their is only one msg for inbound,
check out the color of the icon if it is green( i think it must be green) then go to
T-code SXMB_ADM which is under Admin node in xi server window
--- > Select manage queues then activate queues under action node.
2. Also clear cache by going to t-code SXI_CACHE under configration node
---> Go to XI Runtime Cache menu option and select "delta cache refresh" and " complete cache refresh"
3. if inbound msg icon is red then do accordingly. in this case of red icon there is possibility if bug also
thanks
mandeep virk
**reward if helpful and also update ur status

Pipeline step not displying at SXMB_MONI

Hi all,
I got my newly configured PI box ,every thing is working fine and we tested the test scenario File to File.
file got picked and we able to create new file at receiver folder.
but issue is when i am going to sxmb_moni Tcode I not able to view pipe line step.
I am getting the successful white and black flag for the msg but when i am expending the selected message i not able to find pipeline step under the tree structure.
the only 3 message is displayed is inbound message-->receiver grouping--> response msg.
but when i am going to the XML file on right hand side i able to see that all the step are called properly.
please tell what went wrong
regards,
navneet
Edited by: navneet sumit on Jun 3, 2009 6:12 PM

Hi,
   You have to switch on Logging..in the transaction sxmb_adm - specific configuration
Parameters -
Runtime
LOGGING                                   value - 1
LOGGING_SYNC                          value - 1
for synchronous messages...
If you are using proxies and you want to see the steps from ur source systems then use
LOGGING_SYNC_PROPAGATION   value - 1
LOGGING_SYNC_PROPAGATION            value - 1
regards,
Arvind R

Check Status of a job step

Hi,
Can anyone tell me how to check the true status of a job step.
Using tables TBTCP , or FM BP_JOB_READ what i can come to know is the status of a job step to be 'P" ie Scheduled even when the job containing that step has finished succesfully(Status from TBTCO ).
My Job has 3 steps.
I want to know the status of my 1st job step and based on the status (either Aborted or Finished) i want it to proceed further n execute the 2nd step.and so on.
IS any there way out??
Answers will be rewarded,
regards,
Rohan

Hi,
Checking your job status with SM50 (processor type BTC) is more accurate then SM37. SAP updates the tables TBTCO wheneveryour background jobs status change. If SAP is shutdown, the currentjobs might not be update ontime to the table. (e.g. a background job wasshown as Active (SM37), in fact it real status should be Cancelled.
Look at the function module <b>GET_JOB_RUNTIME_INFO</b>
Regards
Sudheer

Pipeline steps in SXMB_MONI

Hi,
In SXMB_MONI i need a pipeline steps in left side of the XML message.
Please guide me how to do that.
Regards,
sasi.

Hi Look at this thread answered here for your querry
cannot see all steps in SXMB_MONI
REgards
Abhishek

Configuration steps for pipeline steps.

Hi
I want to see all the piple-line steps in moni. For sync interface I am able to see all the pipe line steps. But async interface i am able to see only the below 3 steps. Could you plz tell me what are all the configuraiton steps that I should do to see all the pipeline steps for async messages in moni ?? For async messages is it not possible to see the pipeline steps ??
1. Inbound Message(Scheduled)
2. Receiver groping.(Scheduled for outbound Processing)
3. Response(Processed Successfully)

Palnati,
Set TRACE_LEVEL to 3 (using TA - SXMB_ADM) so that XI will document all processing steps and details
Remember it's good to set the TRACE_LEVEL to 3
only when you need very accurate global trace
but not for a very long time because it can fill your
DEV XI system database very quickly
Regards,

Pipeline Steps and JCo Calls

Hi All,
I wanted a few links which can provide me with indepth knowledge of these two points
1. Pipeline Steps in XI
2. JCo Calls during processing of messages
I am looking specifically to understand the message processing in steps where the Mapping is called and returned to ABAP IE. i mean the Enchanced Receiver Determination / Interface Determination Steps
Rgds
Aditya

Hi Aditya,
Pipeline steps are :
Receiver Identification
Determine which system(s) should participate in an exchange with the
incoming message.
Interface Determination
For each receiver system determine which interface(s) should receive a
message.
Message Branch
If multiple receivers are found, XI will instantiate a new message for each
receiver.
Request Message Mapping
Call the mapping program to transform the message structure to the receiver
format.
Outbound Binding
Bind a specific destination and protocol to the message.
Call Adapter
Send the transformed message to the adapter or proxy
Check this weblog for full details on how a message flows in XI:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
http://help.sap.com/saphelp_nw04/helpdata/en/ff/3eb33b553e436ee10000000a114084/content.htm
Regds,
Pinangshuk.

Proceesing in Pipeline steps is Repeating

Hi Experts,
Here my Scenario is FILE to RFC. In Production XI Server messages are coming from an File system as a file and it can be processed in XI through 6 pipe line steps and processed and send to R/3 and can create a Document number in R/3. Surprisingly after call adapter step again message throtugh pipe line steps is processing repeatedly and again sending to R/3. Like that extra 16 times message processed through Pipeline steps and along with one Document exta 16 Documents are created. In Real scenario the message should be processed only once through pipeline as we know.
and it happened only once. after that the scenario is working fine. one File is Coming and one Document is creating in R/3 Prod.
Can anyone please let me know what could be the reason for happened like this and what i need to do for not happening like this in future.
Thanks in advance,
Regards,
Siva
Edited by: shiva g on Sep 30, 2009 9:27 AM

Hi Raj,
Thank for your reply.
Actually here i can able to see the 6 pipe line steps as 17 times.
And before that and nowalways it is working fine i.e for one File input it is creating one Document at R/3 end.
At one time only it is happend like this.
could you please through some more light on this basis related performance settings in this regard as u said.
Once again thanks,
Siva

Pipeline steps not showing Success indicator

Hi all,
While monitoring messages in the SXMB_MONI, i am getting an error in the pipeline steps. But the previous steps which are exceuted sucessfully, doesn't indicate green success indicator. Can anybody please suggest the possible reason?
Thanks,
Kulwant

Hi ,
Go to SXMB_MONI ......Select the process you are executing and select the tab " display" .... from here you can find out what exactly went wrong in the process
Do let me know if it helped
Regards ,
TJ

Pipeline steps

how to see the pipeline steps, what is the tcode to see

Hello
This is an expert forum, designed for expert users. Please do not post such basic questions. If you wish to learn about XI try the search functionality.
Also, as you are new to the forum please familiarise yourself with the forum [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement].
This thread will be locked and your user will be monitored.
Regards
XI/PI Moderator

Pipeline step

Hi,
I am fresher in sap xi, plz tell me brif what is pipeline step in sap xi,

Hi
Check this weblog for full details on how a message flows in XI:
Understanding message flow in XI
Pipe line is nothing but a series of steps each msg pass through before reaching the target.
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the system that participates in the exchange of the message.
b) Interface Detremination:
For each receiver determine which interface will should receieve the message.
c) Message Split:
If more than one receievers are found, XI will instantiate new message for each receiver.
d) Message Mapping:
Mapping to transform the source message to destination message format.
e) Technical Routing:
Bind a specific destination and protocol to the message.
f) Call outbound Adapter:
Send the transformed message to the adapter or a proxy.

Pipeline Steps in PI

Hi everyone. I want know the Pipeline steps in PI. I go through some threads. But I didnt get the whole idea. Could you Please help me out in this.

Pipeline steps are :
Receiver Identification
Determine which system(s) should participate in an exchange with the
incoming message.
Interface Determination
For each receiver system determine which interface(s) should receive a
message.
Message Branch
If multiple receivers are found, XI will instantiate a new message for each
receiver.
Request Message Mapping
Call the mapping program to transform the message structure to the receiver
format.
Outbound Binding
Bind a specific destination and protocol to the message.
Call Adapter
Send the transformed message to the adapter or proxy.
Regards
Praveen

To raise Alert if Message fails at any of Pipeline Steps.

Hi all,
I need to raise alert if message fails at any of pipeline steps and i need to send alert to TIVOLI and store in TIVOLIdatabase.
Thanks in advance.
Regards
Dinesh

hi dinesh,
for raising the alerts we have to do the alert configuration in the runtime workbench. u can configure the alerts to mailed to a specific mail id or else u can configure it according to the specification required.
thanks,
alpa.

PI Pipeline Doubt : Pipeline Steps in ABAP stack and JAVA stack

Hello
Can anyone please assist me with which stages steps of the PI Pipeline are executed on the Java or the ABAP stack.
Receiver Determination
Interface Determination
Message Split
Message Mapping
Technical routing
Call Adapter
Also can anyone please provide links relating to the PI architecture diagram describing it from ABAP and Java Stack Perspective and not from the Components perspective i.e. Integration Repository and Directory.
Thanks.
Kiran

Hi
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Most of XI pipelines happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Message, Java & XSLT (under Imported Archives) mappings are executed at Java stack;
ABAP & XSLT (in ABAP stack) mappings are executed at ABAP stack.
PI Architecture look threads
Architecture
/message/5802842#5802842 [original link is broken]

Status of Production Order step

Hello Experts,
I have 3 steps in production order and I do confirmation at each step. Is there any report that shows what steps are completed in a list of production order?
Thanks in advance.
Tom

Hi,
You can this through T-code COOIS. There you need to select as "confirmation", then you will get the report based on the confirmed operations.
Regards,
V. Suresh

Waitnig status in a pipeline step

Similar Messages

Maybe you are looking for