like outbound or inbound deliveries (both standard and FLEX) but one of the most popular
is also a standard material movement (from one storage location to another or material status change etc.).
With AII 4.0 material movements can be quite easily integrated with the ERP, R/3 system
via Exchange Infrastructure. This weblog is a quick guide on how to achieve material
movement integration which will be reported in the ERP, R/3 systems.
– basis AII knowledge
– basis XI/PI knowledge (ABAP proxies,mappings, RFC adapter)
1. To start the scenario we need to have at least one EPC material number
on one of the locations in AII. In case you don’t have it yet please commision one EPC tag.
2. The next thing that needs to be done is the location mapping. Basically
what you do here is to specify which locations in the AII have corresponding
storage locations in ERP, R/3 systems and which location can be treated as
a plant. In my example I will move the material from location STRG1 to STRG2
which should cause the movement from SAP storage locations 0001 to 0002.
We can define location correspondance in Location mapping transaction
as shown below. The business system is the name of your ERP, R/3 system
which will be used later on in the activity that sends that data to a specific SAP system.
3. Then you need to create a new rule (it can be a copy of the standard MOV)
in which you need to add activity DEVICE_SEND_INV_MOV_BKND
which is responsible for sending the material movement data to the XI.
you also need to add activity paramter BUSINESS_SYSTEM with the value
taken from the location mapping transaction.
4. Next you need to make sure that your rule will is configured as a Mobile Message Condition
5. The next thing you need to do is the configuration from the XI/PI point of view.
At first you need you need to download XI content for AII 4.0 from http://service.sap.com
which contains message interfaces for AII-XI integration.
Then you need to upload BAPI_GOODMVT_CREATE FM which will be used to post
material movements and map GoodsTransferPostingRequest to this BAPI
and BAPI.request to GoodsTransferPostingConfirmation basically the mapping
below is enough for a simple tests (if you need you can also map BAPI return table of the response).
6. The configuration in Integration Directory is more or less standard (for a sync proxy – RFC interface).
The only thing you need to remember is to add BAPI commit check in the RFC receiver channel
as the BAPI needs to be commited. If your RFC receiver channel does not support BAPI commits
you need to create a BAPI wrapper which you will commit the BAPI for you.
7. Now when you try to do a movement from one location to another you should see a
success message and a message flow (from transaction SXI_MONITOR). Remember
that this is a synchronous message so to see it in XI/PI you need to have
LOGGING_SYNC parameter set (only on DEV sytems).
8. If the material movement was correct and the BAPI created a material movement you
should be able to see the number of the material document (and material document year)
from the application monitoring transaction.
This is a very simple scenario but I’m sure it can be used in many integrated scenarios
and the advantage of using the XI/PI is that you can create the mapping yourself
so you can change the default movemet type (301) for any other
(based on locations for example to post status changes and other not only 301 movement types).