Start of Content Area

Procedure documentation Analyzing a Sequence  Locate the document in its SAP Library structure

Prerequisites

You have performed the steps outlined in the section Choosing Selection Criteria.

Procedure

       1.      Check the status of the sequences listed.

In the sequence overview, you see the following columns:

                            a.      Column

                            b.      Meaning

                            c.      Status

                            d.      This graphic is explained in the accompanying text       Sequence is transmitted

                            e.      This graphic is explained in the accompanying text       Sequence will be transmitted

                              f.      This graphic is explained in the accompanying text       Sequence is terminated

                            g.      Location

                            h.      Logical sequence was created on the consumer side or the provider side.

                              i.      Name of Business Process

                              j.      Name of the software level / application

                            k.      Logical Sequence Key

                              l.      The logical sequence key is not transmitted from the consumer to the provider. (see Technical Sequence Key.)

                          m.      Technical Sequence Key

                            n.      The technical sequence key is requested on the consumer side (Create Sequence Request”), created on the provider side, and then transmitted to the user of the service. The key is identical on both sides and links the different logical sequence keys on the consumer and on the provider side.

 

       2.      Choose a sequence in order to display more details.

In the Sequence Details area, you see the tabs Sequence Header Data, Messages, and Events. The data displayed refers to the selected sequence.

Sequence Header Data Tab

This tab is divided into specifications on the logical and the technical sequence.

Both parts contain information on the current status of sequence processing and the status of the corresponding messages.

You see when and by whom the sequence was created as well as details on the key used and the queue.

Below you will find explanations on the other fields:

                            a.      Field:

                            b.      Meaning:

                            c.      Sequence Error Type

                            d.      This field tells you whether the error occurred in the sequence, in a message, or in the queue. If the cause of error pertains to the sequence, the reason could be that the Create Sequence Request was not transmitted successfully due to authentication problems or incorrect configuration of the Web service on the provider side. If the cause of error pertains to the message, it is possible that the message was not transmitted successfully due to an error in the application on the provider side.

                            e.      Sequence Process Mode

                              f.      Information as to whether the sequence is executed in Remote or Local Process Mode. If you are dealing with a Remote Process Type, the references of the end points are different.

                            g.      Sequence Type

                            h.      Transient (Framework-managed type) or persistent (Application-managed type) sequence

                              i.      If a sequence is created by an application (persistent sequence), the application is also responsible for ending the sequence. A transient sequence – that is, a sequence that was created using the Message Framework – is also terminated by the Message Framework. The end of this sequence is not initiated explicitly by the application.

In the details of the technical sequence, you will find information as to how many messages were transmitted successfully and which messages had an error occurring in them.

Messages

In the Message Status column, you  see the symbol This graphic is explained in the accompanying text if the message has been transmitted successfully to the end point reference of the receiver. A message is flagged for deletion if it has been processed successfully (from the perspective of the sender end point reference). Otherwise, a green traffic light (processing still running) or a red traffic light (processing terminated) will appear.

Each message is displayed with the number, the key, the message status, and the transfer status.

In the Messages tab, you will also find information regarding which service definition a message belongs to.

Events

In the Events tab, you will find an overview of the events that occurred within the selected sequence. For example, if gaps occur during transmission of asynchronous messages in the sequence of the transmitted messages, an event will be triggered. The event process checks whether the existing gap has been closed. The delayed message can then be processed.

The following events are possible:

                              j.      Event:

                            k.      Meaning:

                              l.      WSRM_ACK_REQUESTED_EVENT

                          m.      Confirmation requested

                            n.      WSRM_ACKNOWLEDGEMENT_EVENT

                            o.      Confirmation sent

                            p.      WSRM_INACTIVITY_EVENT

                            q.      Waiting time for new request

                              r.      WSRM_RETRANSMISSION_EVENT

                            s.      Transmission retry

                              t.      WSRM_STOPP

                            u.      Sequence transmission stopped

 

 

 

End of Content Area