As mentioned earlier, you can leverage program /SAPSLL/PRODUCT_DELETE to delete the products or alternatively mark the products for being archived and push them outside the system via the archiving process.
Yes, that's exactly right. The regular transfer includes the "deletion indicator" from the ERP Material Master record. And just as in the ERP system, the deletion indicator makes the GTS Product relevant for archiving, provided of course that it's not still in use.
I have tried this dev. once.. Just thought of sharing the same. Defined some product attributes in GTS to hold some customized flags in Product master-Additional data tab.
For example: Tried updating country flags in the Product master in GTS.
Country flags are updated based on extension of a Material to a Plant in R/3. i.e, Whenever a Material is extended to a Plant in GTS, we use the Plant country code and update the same in Product master.
And similarly, whenever the Deletion flag is setup, the same can be removed. For this to work automatically, just activated change pointers for MARC-LVORM for /sapsll/matmas_sll.
But in my case, it was a customized development.Not really sure, if this is available in standard.
Only client-level is considered. And that's because it's the only level transferred to GTS. No fields from Plant (MARC) or Sales (MVKE) are transferred in the standard mapping. Only field MARA-LVORM is considered, since the other client-level tables (MAKT, MARM, MBEW, MLAN) don't have Deletion Indicators.
Actually, the Deletion Indicator itself isn't transferred to GTS. Instead, if the indicator is set, the "valid to" field (DATBI) is set to the "Date of Last Change" (LAEDA) before the transfer, effectively expiring the Product.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.