Created by Wang, Jerry, last modified on Jan 06, 2017
From SAP help:
Alternative ID types can be defined in the product master and used in business processes instead of the product ID. Alternative IDs therefore allow you to use an identification in your business processes that conforms to industry standards, for example ISBN, serial number, vehicle identification number.
By default SAP has already delivered some standard Alternative ID type and you could find them in this customizing:
For type ALT_NO, it is mapped to settype ISAM_O_VEH_IDS:
In order to use this type in WebClient UI, you have to:
- assign ID type to corresponding product category:
- Also assign the settype ( which is bound to ID type ) to product category:
Then you can maintain this alternative ID in Web UI:
And it is also possible to search against alternative id:
Technically the alternative id is still implemented based on a concrete settype.
Further reading - Design document
The customer product ID is a field in a interlinkage database table. The current implementation of PRDHS/AltID does not support interlinkages. ( Since there’s potentially many ‘Product ID of customer’ per product (each customer has a different product id for the same product), you can’t represent that on a single line. Therefore, the omission from the product detail assignment block. )
There is a report to create the configuration of view PRDHS/AltID: Report CRM_UIU_PROD_CONFIG_ALTID (Transaction CRMM_UIU_PROD_ALTID)
But it works only if the alternative ID type belongs to a single line set type .
Additional document, which describes the steps to create an new Alternative ID:
That field is mostly used to allow our code to stay generic, usually the alternative id is a set type attribute that we point to. You’ll see that we get information from that table on line 32 of CL_ALTID_ALT_NO ->GET_ALTID_FROM_GUID. For ‘Product ID of customer’, set types aren’t being used (it’s using table comm_il_prdcpn).
要获取更多Jerry的原创文章，请关注公众号"汪子熙":