How does a catalogue vendor gets charactarized as a fixed vendor in SRM?

[Former Member]

Dear Expters,

can you please help me understand the standard SRM behaviour (7.0, CS) for the following point:

When a catlogue item is purchased from a third party catalogue platfrom, than the vendor of this catalogue item is displayed as a fixed vendor in the EBP shopping cart, afer the return from the catalogue platform from SRM.

How exactly does the charactarization of the vendor as fixed vendor happens?

I mean, does it happen in a way that during the return from the catalogue platform to SRM, the catalogue platform sends the

content 000019 into the SRM field partner_fct?

Or is the approach completely different and it is done somehow in a way that SRM receives that data from the catalogue platform, than for example understands somehow that this position was sent from a catalogue and based on that decides that the vendor should have the "fixed vendor" partner function?

Thank you.

[ricardo_cavedini]

Hello,

The SRM system behaves as described below:

Limit item:

If a SC is created with a vendor, it is considered as a "Fixed Vendor".

Free text item:

If a SC is created with vendor, it is considered as a "Preferred Vendor".

Catalog items:

When an item is added from a catalog to SC, the vendor is always considered as "Fixed vendor".

It is possible to change the "Preferred Vendor" to "Fixed Vendor" through BADI implementation BBP_DOC_CHANGE_BADI~BBP_SC_CHANGE.

Anyway, if you create a cart using catalog item, vendor will always be considered as fixed.

Regards,

Ricardo

[Former Member]

Hello Ricardo,

great thanks for the detailed answer.

Just an additional question - although you have already stated that a vendor from a catalogue transaction will always be considered a fixed vendor in SRM.

Are there maybe any possibilites that can be used in order to change the vendor from fixed to preferred, even though the item is coming from a catalogue?

The business requirement is the following:

Our catalogue platform provider has - besides the normal vendor catalogues on the platform - also a special functionality of Request for Proposal.

In case the end user has not found the required item in any of the vendor catalogues on the platform, the end user can send RFPs to certain vendors. Once the negotiations have taken place on the platform, the vendor is identified and the end user can return from the platform to SRM, with the item description and the identified vendor.

But what we need to ensure in that case, is that such an RFP vendor does not become a fixed vendor in EBP SC. This is because it should not happen, that a PO is created as a backend document for those SRM items that base on the RFP process. These items need to become a PReq and have to be converted by the Buyer to PO.

Thanks again for your support.

[Former Member]

Dear All,

the question has been solved in the meanwhile.

We have used the DOC_CHANGE BAdI in order to check the EBP SC line item for a certain custom qualifier. This qualifier is sent to us from our catalogue platform provider and we use it in oder to decide when to change the partner function of the vendor from fixed vendor to desired vendor (000039; 000019).

Thank you.