Verb support for the ALE Module is limited by the verbs that SAP supports
through its ALE interface. SAPODA generates the Create, Update, Delete,
and Retrieve verbs in the business object definition. Implementation of
each verb requires knowledge of the ALE configuration within SAP.
SAPODA generates the AppSpecificInfo for the verbs and the
AleOutboundVerbs meta-verb on the parent wrapper business
object. However, it populates only one of the parameters of the
AppSpecificInfo with values: it specifies the business object
handler to use for service-call request processing. For all other
processing, you must manually modify the business object definition to add or
remove specific information:
- When using the business object for event processing, you must specify
values for the following the AppSpecificInfo properties:
- Parent wrapper business object's verb--specify a value for those
parameters that uniquely identify the verb. Depending on the
requirements of your ALE configuration, specify the message type, message
code, and message function. Make these changes after you import the
business object definition into your repository.
- Important:
- SAPODA inserts the AppSpecificInfo value that specifies the
business object handler, which the connector uses only for request
processing. SAPODA does not insert values for the message
parameters. If you are using the ALE Module for event processing, you
must manually add the values for the message parameters.
- Parent wrapper business object's AleOutboundVerbs
meta-verb--a comma-separated list of verbs supported for event
processing.
- When using the business object for request processing, you must specify a
value for the following the AppSpecificInfo properties:
- Parent wrapper business object's verb--specify the package and
classname of the business object handler so that the connector can determine
the appropriate business object handler. SAPODA inserts the following
value into the AppSpecificInfo property of each standard
verb: AppSpecificInfo =
sap.sapalemodule.VSapALEBOHandler.
- When using a wrapper business object to process multiple IDoc parent
business objects, you must add the package and classname of the business
object handler to the AppSpecificInfo property of each verb in the
multiple IDoc wrapper business object.
For each parent wrapper business object, SAPODA generates the Create,
Retrieve, Update, and Delete verbs. For each of these verbs, it
generates the following AppSpecificInfo values:
sap.sapalemodule.VSapALEBOHandler,MsgType=;MsgCode=;MsgFunction=
To support multiple message types that map to the same basic IDoc
type:
- Generate as many business objects from the same IDoc as the number of
message types you want to support. Note that the same business object
needs to be saved with different names.
- Configure the verb apptext to set "MsgType= xxxxx" to the
proper message type in each object. The business object level ASI will
be set to the same IDoc type in all of these objects.
- Perform the necessary configurations in SAP. Maintain transaction
WE82 to map message type to basic type.
Using the previous configuration, a single instance of the adapter suffices
to support multiple mappings of the same basic IDoc type to various message
types.
Two instances of the adapter cannot use the same set of MQ Queues for event
processing. Create a set of MQ Queues for each adapter.
The syntax of the AppSpecificInfo property of the parent wrapper
business object's verb differs depending on whether the business object
represents an application event or a service call request:
[BOHandler],MsgType=messageType;MsgCode=[messageCode];MsgFunction=[messageFunction]
- Note:
- The connector matches the values in the control record with the values
specified in the verb's AppSpecificInfo property to determine
the verb.
BOHandler[,MsgType=messageType;MsgCode=[messageCode];MsgFunction=[messageFunction]]
- BOHandler
- Specifies the request-processing business object handler; the value
defaults to the following:
sap.sapalemodule.VSapALEBOHandler
- MsgType
- Specifies the message type configured for the IDoc in ALE
- MsgCode
- Specifies the message code configured for the IDoc in ALE; the
connector requires a value only if MsgType does not uniquely
identify the verb; however, specify a value if required by your ALE
configuration
- MsgFunction
- Specifies the message function configured for the IDoc in ALE; the
connector requires a value only if MsgType and MsgCode
do not uniquely identify the verb; however, specify a value if required
by your ALE configuration
In the AppSpecificInfo property of the parent wrapper business
object's AleOutboundVerbs verb, specify those verbs the
connector should support for application-event processing, separating verbs
with a comma.
- Important:
- SAPODA generates values for the Create, Retrieve, Update, and Delete
verbs. After the definition has been generated, you must manually
delete those verbs that you do not want the connector to support.
The following example instructs the connector to support the Create and
Update verbs for processing application events:
[Verb]
Name = AleOutboundVerbs
AppSpecificInfo = Create, Update
[End]
