Detalied explanation of each workflow is not in scope of this document. Please see SAPMEINT application help on http://help.sap.com for details. Each of these workflow types has certain set of attributes. Below is an example of BOMMAT03 workflow, a Standard workflow, which is used for BOM integration.
As shown in the above figure, each transaction or XSLT attribute is divided into three categories:
Partners/Customers can write their own custom XSLT or transaction/java plug-in class and use it in the existing workflows. Details on how it can be achieved are covered in document below.
The custom XSLT's are written in a similar way how it was done in SAP ME 6.0.
Steps to create and upload custom XSLT.
Note: The MII workbench can also be used to customize the XSLT’s. The XSLT’s provided by SAPMEINT under Web tab will be available in read-only mode. For doing customizations on top of it, the user has to copy the XSLT under a local project manually. The XSLT then can be edited and saved.
3. To use the custom XSLT in the workflow, just specify the fully qualified path in the following format as partner/customer XSLT.
WEB://<Project name>/<Folder Structure>/<XSLT name>
EXAMPLE
This example shows where in customer is trying to integrate custom Z_BOMMAT03 instead of BOMMAT03 which has an additional user field Z_BOMMAT03 /IDOC/ E1STZUM /Z_USER) which needs to be mapped to custom data in SAPME BOM as CUSTOM_FIELD.
So the corresponding BOMRequest.xslt also needs to be modified to map the Z_USER field from idoc to custom field. Please see the snippet below, how the xslt needs to be modified.
Now the xslt can be upload as specified in step 3.
From SAP ME 6.1, with co-located enviornment (SAP ME and SAP MEINT running on same server), SAPMEINT is enabled to call SAP ME PAPI's directly. There is no need to make a web service call to PAPI's using SAPMEINT transactions. So in SAP ME 6.1 all the service transaction plugins are replaced from MII transaction to JAVA plug-in for all the existing inbound workflows.
The custom java plug-in can be used for various purposes except for making RFC/BAPI calls. Custom transaction (explained later in the document) is recommended for making RFC/BAPI calls to ERP because SAP MII framework provides a set of action blocks JRA/JCO for doing this.
Steps to create and upload custom java plug-in class.
2. Navigate to “MyComponents” software component and add SAPMEINT as dependency.
3. Create a new development component of type Java “meintextension” as shown below. Right click MyComponents -> New -> Development Component.
4. Add xapps/me/integration/action DC and xapps/me/integration/libraries DC as a dependency to the newly created “meintextension” DC as shown below.
5. Now a new java plugin class can be created. The new class should implement processMessage method of PluginInterface. The signature of processMessage method is shown below
All the business logic should be written inside processMessage method of the plugin. Below are some usecases for this plugin.
Code snippet for Java plugin
Package Name: com.sap.meint
Class name: ERPItemHandlerExtension
Implements processMessage method of PluginInterface
6. After creating the java plug-in class, export the project as a JAR. Select export destination as JAR file and click Next.
Browse and specify the jar name and click on finish as shown below. Leave other entries as default.
The exported JAR will now be available in the file system at the specified directory structure.
7. Upload the JAR in SAP MII.
a. Go to SAP MII Admin screen. Navigate to System Resources -> Custom Actions.
b. SAP MII has extended the functionality to upload dependency for the already deployed actions. Select the deployed SAPMEINT custom
action named sap.com~xapps~me~integration~action~actions.mii-actions.jar and click on Upload Dependency.
c. Browse and choose the JAR created in Step 6. The dependency is added as shown below.
8. The java plug-in created in Step 5 can now be used in SAPMEINT workflows. The URL has to be in the following format.
java:<Package Name>.<Class Name>
d. Save the changes made to the workflow. At the run time, the custom java plugin will get executed instead of the default Service transaction.
Note: MII transactions can still be used in SAPMEINT workflows. Java plugin's don't completely replace MII transactions rather it is another way of doing customizing in SAPMEINT. Java plugin's are recommended over MII transaction because of better performance.
The custom MII transactions are written in a similar way how it was done in SAP ME 6.0. But from SAP ME 6.1 there is a new custom action block available to call SAP ME API's directly from SAPMEINT instead of making a web service call.
The custom transaction can be used for various purposes depending upon the requirement. Some of the use cases are as follows:
Steps to create and upload custom transaction.
Visiprise/ERPShopFloorIntegration/frame/workflow/IPlunginHandler
b. By modifying the existing transactions: Copy and paste the existing transaction in the local project structure and do the customizations on top of
it. In this case, user will not have to write the entire implementation from scratch.
Transaction Input/Output Parameters
Property Name | Type | Description |
inputXML | Input | The input XML passed to “custom transaction” by SAPMEINT. |
params | Input | The value of the “custom transaction Params” passed to “custom transaction” by SAPMEINT. |
plant | Input | The plant value passed to “custom transaction” by SAPMEINT. |
recordId | Input | The id of the Message Queue passed to “custom transaction” by SAPMEINT. It is nothing but SAPMEINT_MESSAGE _QUEUE_ID. |
typeId | Input | The document type value passed to “custom transaction” by SAPMEINT. |
status | Output | The status of “custom transaction”. Developer should set this to one of the following values:
|
message | Output | Developer can set the correct error message when this transaction fails for some reason. |
outputXML | Output | Developer should set the outputXML and this outputXML will be used as an input for further steps in the workflow. |
3. To use the newly created transaction in the workflow, just specify the fully qualified path in the following format as partner/customer transaction.
<Project name>/<Folder Structure>/<Transaction name>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |