Punchout Catalog product ID's not returning to SC

[Former Member]

Hi Gurus,

I am facing an issue where the vendors UNSPSC codes in the punchout catalog are not being returned into the SC.  We have the UNSPSC codes in comm_hierarchy which have come over from our ECC system.  For some reason the system is defaulting the product category from the default in the extended attributes.  We have done an initial debug and can see the product id from the catalog, but then not sure what to look at to figure out why this is getting replaced with the default from the extended attributes.  Any help is appreciated.

Thanks,

Jeff

[konstantin_anikeev]

Hi Jeff,

comes UNSPSC from catalog via OCI?

Which UNSPSC has your material number in COMMPR01?

Regards

Konstantin

[Former Member]

Kanstantin,

These are items from a vendor punchout catalog so this would be a free item and not material numbers that we are maintaining.

Thanks,

Jeff

[konstantin_anikeev]

Hi Jeff,

So, it can be, that vendor catalog sends no UNSPSC. In this case a default UNSPSC is taken.

If you need your own logic - you may need to implement BBP_CATALOG_TRANSFER BADI and fill UNSPSC by yourself.

Regards

Konstantin

[Former Member]

Hi Konstanstin,

In debug we can see that the vendor is passing the UNSPSC code but then somehow SRM is dropping this and replacing it with the default from our attributes.

Thanks,
Jeff

[konstantin_anikeev]

Hi Jeff,

try to double chek it... May be leading zeroes, small/capital letters or something like this.

Is transferred UNSPSC allowed for the user in PPOMA?

Regards

Konstantin

[Former Member]

Hi Kanstantin,

We still have not been able to figure this issue out.  Now it seems to work for 1 punchout catalog supplier and not another.  Seems that UNSPSC code ABC comes back for punchout catalog supplier A, but not for supplier B.  My developer has confirmed in debug that he can see the UNSPSC code trying to come back and then in /sapsrm/cl_pdo_bo_sc===========cm05t changes the it to what is assigned in extended attributes.

Thanks,

Jeff Miller

[konstantin_anikeev]

Hi Jeff,

all available/possible UNSPSCs must be assigned as an extended attribute (placeholder * will also work, but at least one real UNSPSC).

What method corresponds to /sapsrm/cl_pdo_bo_sc===========cm05t ? Do you have a screenshot?

Regards

Konstantin

[Former Member]

Hi Konstantin,

Just got a little bit more info.  One vendor is not sending over the std schema UNSPSC and thus the UNSPSC code is coming through.  The vendor sending over the std schema UNSPSC is the one that is being converted back to the users default attributes.

Where and how can I maintain UNSPSC std schema for material group in ECC?  Also what affect will this have in ECC if this get assigned R3MATCLASS?  Not sure where this is at in ECC.  Would this then change how the system acts for the vendor not sending over the schema UNSPSC?

thanks,

Jeff

[konstantin_anikeev]

Hi Jeff,

Maintain Material Groups in ECC via transaction OMSF or WG21.

Assignment Material to Mat.Group (UNSPSC) is made in Material maintenance transactions (MM01, MM02).

Check the link https://websmp210.sap-ag.de/~sapidb/011000358700000207252013E/OCI_50_EN20130228.pdf

That's OCI 5.0 Definition (Open Catalog Interface).

Could you please check page 13 and say, what fields come from vendor and how do the filled.

Regards

Konstantin