Hierarchy
AIN (Software Component) AIN 710: Add-On Installation⤷
AIE-AII (Application Component) Infrastructure⤷
/AIN/PUBLIC_SERVICES (Package) Auto-ID Released Services
IMG Activity
| ID | /AIN/PUBSERVICE_POBJ | BAdI: Generate Object Quantity for Aggregation |
| Transaction Code | /AIN/46000015 | (empty) |
| Created on | 20080326 | |
| Customizing Attributes | /AIN/PUBSERVICE_POBJ | BAdI: Generate Object Quantity for Aggregation |
| Customizing Activity | /AIN/PUBSERVICE_POBJ | BAdI: Generate Object Quantity for Aggregation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /AIN/PUBSERVICE_POBJ |
Use
This Business Add-In (BAdI) is used in the SAP Auto-ID Infrastructure component. You can use this BAdI to retrieve quantities and related characteristics (like product, unit of measure, GTIN, GRAI, batch number) and their values per physical object (that is, RFID tag). Those quantities are aggregated to calculate document line item quantities. Therefore, document line item attributes (like product and unit of measure) are matched to characteristic values of the physical objects (see also IMG activity Define Physical Object Categories).
The order of the characteristic values within the return table is sorted by corresponding characteristic names (for example, PRODUCT).
To save database space, characteristics are not explicitly assigned to physical objects, but rather via characteristic combinations. If a combination is required that does not exist, it can be generated and inserted into the combination table within the BAdI interface. The combinations are unique and must not be duplicated.
You can also use this BAdI to allow counting of tagged containers (for example, tagged cases which contain tagged items), since by default only lowest level items of the packing hierarchy (the tagged items in this case) are considered for aggregation.
Requirements
Standard settings
You only have to implement this BAdI if characteristics and their values cannot be retrieved from object ID (like GTIN from EPC SGTIN) or from object context attributes (like batch number) or if the quantity is not '1'.
- In the standard system, there is no activated BAdI implementation.
- The BAdI is designed for single use.
- The BAdI is not filter-dependent.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
See also:
The BAdI uses the interface /AIN/IF_EX_PUBSERVICE_POBJ. For more information, display the interface in the Class Builder.
Example
Usually the quantity is '1', the characteristics are product ('PRODUCT') and the unit of measure ('UOM'). However, if an RFID tag refers to multiple products (i.e. associated GTIN is used in multiple products), GTIN could replace product and unit of measure as characteristic.
Example for :
- Quantity: '1'
- Characteristic combination GUID for the combination of product, unit of measure, and batch number
- Characteristic value for product: 'Product GUID'
- Characteristic value for unit of measure: 'EA'
- Characteristic value for batch number: '4711'
Example for characteristic combination:
- Characteristic combination GUID
- 'PRODUCT'
- 'UOM'
- 'BATCH_ID'
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/PUBSERVICE_POBJ | 0 | /AIN/R4D0000002 | Application |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080326 |
| SAP Release Created in | 700 |
