Backend Source of Supply not supported for Direct Material in SRM

[Former Member]

Hi ,

When creating S/C or PO in SRM for Direct Material , backend Source of Supply ( i..e Purchasing Info Record or Backend Contracts ) not availble to select as a sourc of supply .

In our case, we are planning to maintain the sourc of supply (PIR or Contracts) in back end MM system only , then how can pick up the same ?

Can anyone please suggest on this .

Regards

NAP

[former_member183819 · Accepted solution]

refer this thread eventually my answers

Classic:Info record / ECC contract / vendor list-

ECS:- Local contract / vendor list or bring ECC contract to SRM via report and lock the backend contract.

Vendor(new supplier list) list dont support local contract . it supports only ECC contract .

E BBP_PD 351 Local contracts are not permitted in the vendor list

Muthu

[Former Member · Accepted solution]

Hi Muthu,

Thanks for reply. Sorry , but I am not cleared yet.In my case ,when we click on "OADM" ,sysem only prapose V/L, but excluds the Vendor with Backend Contracts

Why it is excluding othe Vendor with backend contract ?

Can you please suggest on this .

REgards

NAP

[former_member183819 · Accepted solution]

check logical system of you VL when you refer a contract.

make ensure that your VL has activated or released.

you must get it or debug for a while.

Muthu

[Former Member · Accepted solution]

I am afraid , but I enetred correct logical system in VL and same had released and all items are activated as well.

What should be another reason ?

[former_member183819 · Accepted solution]

check with SAP . Create oss message and clarify the same

Muthu

[Former Member · Accepted solution]

Hi Muthu, Prashant and All,

SAP is Changing contain of the www.help.sap.com for on Supplier List topic , for better clarity. I got the below reply from SAP.

The "Integration" section of the document "Sourcing Using Supplier
Lists" has been updated with the following text:
o Selection of back-end contracts from a supplier list is supported
only in the Classic deployment mode in SAP SRM.
o Direct material procurement is supported in SAP SRM shopping cart
or purchase order only in the Extended Classic deployment mode in SAP
SRM.
This change is implemented in SAP Note 1557130 for SAP SRM 5.0. The
documentation for SAP SRM 7.0 and 7.01 is also updated. The exports for
these releases are scheduled for March and June. You will then be able
to see the corrected documentation on help.sap.com.
If you require anything further, please let me know.
Thanks and regards,

Thanks to SAP, for taking this action, so that now no one will confuse on this issue. It woould be far better if SAP think and do something for this DIRECT MATERIAL for picking backend SoS and ECS scenarion for same. I'll suggest to SAP in this OSS Messgage.

Thanks

NAP

[former_member183819 · Accepted solution]

Thanks Narendra for good follow up with SAP and thanks for written statement from SAP, Good Job.

one of your another issue is still pending . service contract source of supply is not availble for shopping cart . till SRM 550 the issue was there and resolved by one piece of code and now the same problem exist in SRM 700 .

please update that one too ..

[Former Member · Accepted solution]

Thanks Muthu.

In my case now in SRM7.0 , system pick up the Service Contract in ECC as a SoS , but this price is of Contract line item and not indivigual Service Line same is raised with SAP.

Lets see what SAP replies ?

What exactly issue you guys facing with Service Contaract ?

Plz update me.

Thanks

NAP

[Former Member · Accepted solution]

Hi Muthu and All,

I gotta reply from SAP, but its disappointing...

It is as below

Dear ....,

I am taking over this message.
Actually ....mentioned the price order because system is assumming the
contract price as a whole and not only for the service master item.
Since backend contract has been assigned as source of supply, its total
net price (330,00) will be assumed as shopping cart price as well and
not only the line item which has a service master assigned (300,00).
When SRM checks backend contract, it will check whole document and not
only one item.

This is because SRM would not be able to calculate the pricing based on
the complex pricing conditions maintained in the backend.

Best regards,
SAP
Hi ...,

I think there is some confusion in your understanding of this issue.

We had deployed Classic scenario and for respective Service 3000011,
ECC contract 4600000036/10 is maintained in the B/E system and you are
talking about the priority of SoS i.e (Local) Contract Price,
Interlinkage, Product Price..Etc , which are Local SoS in the SRM
system, which is valid for the Extended or Standalone scenario and not
relation to Classic scenario.

Our issue is not about priority of SOS. Our issue is, system is NOT
picking the indiviugual service line items price from Contract (i.e.
Rate/Price of Service 300011 is 3 AUD), but picking the NET PRICE OF
ITEM IN ITEM OVERVIEW SECTION (i.e. 100 Qty *3 AUD [Service 300011] +
15 Qty *2 AUD [Service Free Text] = 330 AUD).

How system can pick up the Total amount of ALL the individual services
(i.e. addition of the entire services amount (i.e. Qty*Price) in
Service tab page) in SRM Shopping Cart? This is absolutely wrong and
not logical!

If you still not understood the issue, then please feel free t ask to
me.

Would you please check in detail and suggest the correct solution on
same at the earliest?

Thanks
......

Do anyone have solution on this to get the service price from ECC contarct at service level by doing some enhancment ?

Regarsds

NAP

Edited by: Narendra Patil_111 on Feb 21, 2011 9:02 AM

[former_member183819 · Accepted solution]

hi

remove their names .. in your last reply

normally indeed price pick from contract while creating po only . ( contract price will not copy into the shopping cart like PR)

Is the final po has picked from contract or not.

however i will restudy your thread and come back to you.there are some incidents in srm 700 service contracts are not available for shopping cart requesters to assign a sos.

[Former Member · Accepted solution]

Hi Muthu,

Any news on this ECC Service Contact ?

Regards

NAP

[Former Member · Accepted solution]

Hi Muthu,

Any news on this ECC Service Contact ....?

Regards

NAP

[yeushengteo]

Hi,

Enabling backend contract as a SOS for direct material SC item is feasible in SRM 7.0:

For now, please make explicit enhancement at the end of the following routines. Please note this is not a encouragement for you to bypass the standard. Hence you should only do it after a detailed understanding on the implication.

- LBBP_BD_COMPLETEF29

>>>

• Change logical system to backend logical system

IF cs_item-subtype EQ c_subtype_i_dp AND

cs_item-be_move_type IS INITIAL.

cs_item-be_log_system = <ls_ilogsys>-logical_system.

cs_item-be_move_type = '201'.

ENDIF.

>>>

- class CL_BBP_BS_MAP_SC2PO method MAP_ITEM

>>>

• 1. PO created from Direct material shopping cart (SUBTYPE = DP)

• 2. PO created from Bid Response with SUBTYPE = DP

IF ( ( IS_item-subtype EQ c_subtype_i_dp ) OR

( IS_item-subtype EQ c_subtype_i_dp AND IS_item-ext_quote_id IS NOT INITIAL ) ).

• Clear acctasscat field

mc_assign_x ls_be_item acctasscat space.

es_be_item = ls_be_item.

IF es_be_itemx IS REQUESTED.

ls_be_itemx-po_item = ls_be_item-po_item.

ls_be_itemx-po_itemx = c_on.

es_be_itemx = ls_be_itemx.

ENDIF.

ENDIF.

>>>

- class /SAPSRM/CL_PDO_BO_SC method LOGICAL_SYSTEM_GET_NEW

>>>

• Change logical system to backend logical system

IF cs_item-subtype EQ /SAPSRM/IF_PDO_OBJ_TYPES_C=>GC_SUBTYPE_I_DP.

cs_item-be_log_system = ls_com_item-logical_system.

ENDIF.

>>>

This limitation will be resolved at a future enhancement in SRM 7.0.

Best regards.

YS

[Former Member]

Thanks Yeu. Appriciate your input.

This is for Dircet Material.

But at this moment , I'm worried about Picking of corrcet Service Price form ECC Service Contract in Classic Senario in SRM7.0. Do you have any inputs on this ?

REgards

NAP

[yeushengteo]

Hi,

Classic scenario is a strong foundation built with SRM for ERP in both material and services items. If nothing works and you have difficulty selecting service item in SRM purchasing, you can report to SAP for assistance.

Direct material is something not supported even till now in SRM 7.0 EHP1. Hence you cannot request SAP support assistance unlike the one above.

Regards.

YS

[Former Member]

Hi Yeu Sheng,

Thanks for sharing the code. I assume something like that will be available in EhP2?

I do have an issue though. If a Shopping Cart is being processed via the Sourcing Cockpit, an account assignment is added again to the XML message being sent to ECC. This does not happen when the PO is created directly after the approval of the SC. Any suggestions on how to prevent that from happening?

Kind regards,

Bastiaan

[former_member183819]

Hi

Are you in Classic mode or extended mode ?

If the SRM system is connected to backend system, you must see source of supply in SRM .

SRM just queries backend source of supply in the backend system in the classic scenario.

if you activate ECS inorecord , backend contract are not available as source of supply.

FM BBP_PDC_SRC_DETERMINE - debug the FM

Muthu

[Former Member]

We are in Classic ModE AND For Indirect Materials there is no issue while making S/C.

But this issue is when we click on "ORDER AS DIRECT MATERIAL".

NAP

[former_member183819]

Yes. you are correct . i am also confirm this. SRM 550

It will not propose backend source of supply for direct matrials.

Although you create shopping carts for back end materials,

Enterprise Buyer is the leading system in case of direct procurement.

This means the system behaves according the extended classic scenario.

It really treated like Extended classic scenario when you order as DIRECT .

create one vendor list in SRM and refer the backend contract same via vendor list.

Muthu

[Former Member]

When "Order as Direct Material" is selected, system will treat it as "Direct Material" without accounting tab and tries to create local PO as in ECS. This is standard behaviour in both Classic and ECS. Hence backend sources will not be proposed as SOS.

If you want to create classic PO for this scenario, you need to make some enhancements like disable "Direct Procurement" flag and enforce dummy accounting details.

Regards,

Jagadish

[Former Member]

Thank you for reply.

I tried, but .... . I created V/L for Xyz Material for 2 vendors, one with Backed Contract ..but when we create the S/C for that Material ,system only prapose V/L,when we click on "OADM" and excluds the Vendor with Backend Contracts

Why it is excluding othe Vendor with backend contract ?

Can you please suggest on this .

Regards

NAP

[former_member183819]

OK.

you may need to transfer contract from ECC to SRM via initial load job if you want to use for OADP .As already Jagdish confirmed the same.Thanks Jagdish

since it fully treated as Extended Classic Scenario .

the below are real source of supply in Extended classic scenario.

vendor list

local contract

Muthu

[Former Member]

Great thanks to Muthu and Jagdish.

Jagdish- one further doubt ......after doing all enhancement to treate Direct Mat as Indirect Mat......as suggsted by you...., still we need to initial upload the backend Contracts to use as a SOS for Direct Materials (and inturn converted indirect Material by enhancment )?

Regards

NAP

[Former Member]

As Muthu said create VL with reference to backend contracts and this vendor (from VL) will be proposed as the SOS and you should be able to create backend PO. In this case you dont need to upload contracts into SRM.

Regards,

Jagadish

[Former Member]

Hii Jagdish,

Thanks for reply. Sorry for repeatating.

But my doubt still not solved. . Is this valid simply using converting Direct Material to indirect Material by suggested enhancment and simply Direct Material as well ?

Regards

NAP

[Former Member]

Hi Patil

Is this sisue solved for you.? Even we are facirng similar issue.

can you share how was it got resolved.

Regards

Prashanth K Saralaya

[Former Member]

NO Prashanta,

It is still pending for me . i just raised OSS message to SAP ...but SAP saying that

" I checked and found that in the classic scenario , Direct Materials cannot use backend contracts. The behavior described above is in accordance with the system design. Only local sources of supply (local contracts and interlinkages) can be

used in the direct material scenario, as well as as in the extended classic scenario . Therefore the above error message which you get "Specify a valid contract" is valid."

I replied with the doubt that "Thanks for reply but we are not convenience, since what we learnt from

different SAP Blogs, Below SAP help and SRM Experts discussion forum

is, for Ext Classic Scenario (since for direct materials it always

tales by default Ext Classic Scenario, although we implemented Classic)

Local SRM contract and Supplier List are the possible Source of Supply.

As per SAP help documentation for Self-Service Procurement (Extended

Classic) on below link

http://help.sap.com/saphelp_srm70/helpdata/en/e0/f6be5157a24340bf7b1279854a52e1/frameset.htm u201CYou can assign the sources proposed by the

system to items automatically (for example, if there is a single

contract for the item being procured) or manually in the case of a

quota arrangement, contract, or supplier from a supplier listu201D

As per SAP help documentation for Sourcing Using Supplier Lists on

below link,

http://help.sap.com/saphelp_srm70/helpdata/en/d8/33ec56f17f4404806072749f7e764f/frameset.htm u201CIn supplier lists, you can also manually allocate

back-end contracts from specific systems. This enables more effective

sourcing for back-end contractsu201D

In the Supplier List there is facility to enter the ECC Contract

Number. Supplier List donu2019t support local SRM contract. It supports

only ECC Contract /item.

As per your reply, do you mean to say that Source List is not a valid

Source of Supply for Direct Material in Classic Scenario (i.e. Ext

Classic scenario)? If not, then why the backend ECC Contract displays

as a Source of Supply, when we check the u201COrder as direct Materialu201D?

Kindly suggest"

Lets see.what SAP now replies.

Simultaniously I'm looking some enhancment

If you have nay update/soultion then please share with me.