Hierarchy
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/ACTIVITIES (Package) Auto-ID Activities
IMG Activity
ID | /AIN/ACTVT000001 | BAdI: Modify Observation Related Data |
Transaction Code | /AIN/71000022 | (empty) |
Created on | 20050822 | |
Customizing Attributes | /AIN/ACTVT000001 | Modify Observation Related Data |
Customizing Activity | /AIN/ACTVT000001 | Modify Observation Related Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /AIN/ACTVT000001 |
Use
This Business Add-In (BAdI) modifies device message data before it is processed by an activity. The BAdI works with messages from both fixed and mobile devices.
Requirements
A device must trigger a rule delivered by SAP Auto-ID Infrastructure (SAP AII).
Standard settings
The BAdI has the default implementation /AIN/CL_IM_DOC_DTM for automatic document assignment. This process automatically assigns a document to an SAP AII transaction without requiring you to manually change the document. There are two variations of this functionality:
- Document assignment for non-integrated documents
In this case, the document is automatically assigned to the current transaction based on the most recent observation providing you have defined a default action type for the document type / device group role combination. For example, if a PACK transaction has been executed before, and document D1 is assigned to the transaction, when the proper parameter is set, D1 can be automatically used for all following transactions such as MOVE, LOAD, and so on.
- Document assignment for integrated documents
In this case, the document comes from the backend system and SAP AII performs document determination based on the data in the backend document. The document type and action type must be assigned to the device group role as a prerequisite. For example, if SAP AII receives a PACK document D2 from the backend system, when the proper parameter is set, D2 can be automatically used for the current PACK transaction.
Activities
Example
The BAdI can be used for the following:
- Filtering of IDs (that is, to delete entries from field EPC_DATA in parameter CS_MESSAGE)
- Document determination
- Object hierarchy determination
- Validation of device message data
You can also record validation information in the application log. To do so, you must populate the table ET_LOGMSG with the validation messages.
- Stopping a rule by raising an exception defined by the interface /AIN/CX_ACT_PUB
See also
Methods
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /AIN/ACTVT000001 | 0 | /AIN/R4D0000002 | Application |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20070221 |
SAP Release Created in | 400 |