Integration Framework

Processing Atom
Put to Internal Queue

Last Modified: Mai 5, 2014

Table of Contents
1 Parameters ......................................................................................................................... 2
2 Functions ............................................................................................................................ 3
Copyrights, Trademarks, and Disclaimers .............................................................................. 5

Put to Internal Queue

In the process flow, use the Put to Internal Queue atom to send messages to an internal queue
of the integration framework server.

The functional atom Put to Internal Queue is of type simple call. You therefore do not need a
predecessor transformation atom to prepare the data you send to the queue. If you need a
predecessor transformation atom to calculate data to hand over as an inbound XML document
to the internal queue, add this transformation atom in front of the Put to Internal Queue atom.

1 Parameters
Scenario Step Identifier
This field is read-only and displays the name of the scenario step for which you develop the
process flow.
Atom Identifier
This field is read-only and displays the name of the processing atom. The name is unique and
the system automatically generates is when creating the atom. The name follows the convention
atom<no>, where <no> is a unique number. This name is important. It is the identifier for
subsequent atoms for accessing data of the atom using the XPath expression for example
/vpf:Msg/vpf:Body/vpf:Payload[./@id=atom2]/*.
Description
The integration framework automatically generates the description for the atom during atom
creation. You can change the description. First and foremost it serves as a comment to describe
the task executed in this atom. In the graphical flow, the integration framework displays this text
as mouse over. You can also use the description to change the default label the integration
Public
2014 SAP AG or an SAP affiliate company.
All rights reserved

framework displays on top of the atom. For introducing an individual label, add the new label in
brackets at the end of your description. The system displays the string this is my
comment[my Label], for example as my Label on top of the atom. Note that your label can
only have ten digits.
Queue
The integration framework automatically enters #Q.INB_IQ_INTQ_ASYN_QS.0010000000 as
the default. 0010000000 is the SysId of the integration server. Do not change this entry.
Stream
This parameter is mandatory. It is the identifier of the internal queue. Enter the scenario step
identifier of the scenario step that the integration framework triggers with messages in this
internal queue.
Input
Select the identifier of the atom, which creates the messages you want to put into the internal
queue. If you do not select an atom, the integration framework uses the inbound message of the
ToQueue atom.

2 Functions
To open documentation, describing the concepts of variables and properties and how to use
them in the context of the process development, click the button.

The integration framework provides context-based documentation. If documentation is available,

the system displays the documentation icon. The greyed out icon indicates still missing
documentation. To open documentation, click the icon.
[Save]
To save the parameter definitions, click the [Save] button. The integration framework stores all
settings in the process flow definition document (vBIU.bfd). To open this document for your
reference, click the
icon placed on the start atom of the flow.
[VarL]
To add, change or delete local variables, click the [VarL] button. Local variables are valid for a
scenario step only. In the scenario step all processing atoms can use them. You can assign
fixed literals or an XPath running against the incoming message at runtime before the system
calls the process flow. In the process flow the value is fixed and you cannot change it. You can
use local variables in your XSL coding or in the parameter definition for processing atoms. To
open documentation, click the

button.

[VarG]
To add, change or delete global variables, click the [VarG] button. Global variables are valid for
all scenario steps of a scenario package. In the scenario steps all processing atoms can use
them. You can assign fixed literals or an XPath running against the incoming message at
Public
2014 SAP AG or an SAP affiliate company.
All rights reserved

runtime before the system calls the process flow. In the process flow the value is fixed and you
cannot change it. You can use global variables in your XSL coding or in the parameter definition
for processing atoms. To open documentation, click the

button.

[Close]
To close the user interface of the processing atom, click the [Close] button.

Public
2014 SAP AG or an SAP affiliate company.
All rights reserved

Copyrights, Trademarks, and Disclaimers

Copyright 2014 SAP AG. All rights reserved.
The current version of the copyrights, trademarks, and disclaimers at
http://service.sap.com/smb/sbocustomer/documentation is valid for this document.

Public
2014 SAP AG or an SAP affiliate company.
All rights reserved