Hierarchy
AIN (Software Component) AIN 710: Add-On Installation⤷
AIE-AII (Application Component) Infrastructure⤷
/AIN/IDMAPPING (Package) Auto-ID ID Mapping
IMG Activity
| ID | /AIN/IDM_PROD_ID_GET | BAdI: Get New Product ID and Description |
| Transaction Code | /AIN/46000007 | (empty) |
| Created on | 20080303 | |
| Customizing Attributes | /AIN/IDM_PROD_ID_GET | BAdI: Get New Product ID and Description |
| Customizing Activity | /AIN/IDM_PROD_ID_GET | BAdI: Get New Product ID and Description |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /AIN/IDM_BADI_PROD_ID_GET |
Use
This Business Add-In (BAdI) is used in the SAP Auto-ID Infrastructure component within the SAP object event repository.
You can use this BAdI to construct an SAP Auto-ID Infrastructure product ID and a description from an EPCIS EPC class URN. The EPC class URN is a URN form of representation of GTIN or a GRAI and is modeled in the repository as a product. This BAdI is invoked during the processing of an inbound event capture notification (ECN) message in the repository whenever the message contains an EPC class for which a product does not exist in the system.
SAP object event repository is supposed to receive event capture messages from various sources. It is conceivable that the ECN message contains an EPC class that does not exist in the repository. In such cases, the repository stores this EPC class by creating a product. If the EPC class contains a GTIN, the repository creates a product ID, ECGT<GTIN>, with description EPCCLASS: <GTIN> and base UOM EA with the GTIN assigned to the base UOM. If the EPC class contains a GRAI, it is also handled similarly (product ID begins with ECGR instead of ECGT).
However, you may have your own convention for naming product, and you can return the ID and description of the product you want to be created for this new EPC class in the BAdI.
Requirements
Standard settings
- 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.
Example
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080307 |
| SAP Release Created in | 700 |
