cancel
Showing results for 
Search instead for 
Did you mean: 

UOM issue when source determination via contract

Former Member
0 Kudos

Dear all,

We are in SRM 7.0 SP11 classic scenario with ECC 604 SP8. In SRM are creating SC with backend contract as source of supply. We are facing the following issue:

Backend contract exists for a particular product category with two line items - first item UOM PC, second item UOM PAC.

A SC created for this product category with two line items - first UOM PC, second item UOM PAC.

The SC fails with "backend application error" when transferred to backend - "06 739 Base unit PC and Order unit PAC incompatible"

It appears the validation against the contract lines always picks the first line items with e.g. UOM PC and considers all other SC's line items to go against the same contract line item (with UOM PC) and not against the other contact line item (with UOM PAC). In SRM source of supply for all SC line items the same contract item is displayed regardless the UOM.

UOM PC and PAC are set up in both SRM and backend CUNI the same way.

Any help would be appreciated.

Thank you.

Source of supply is not redetermined for new or changed SC items in case UOM changes. It actually does get redetermined for changes in Product category. Any idea where to look at? Thank you. Message was edited by: Karel Reis

Accepted Solutions (1)

Accepted Solutions (1)

former_member183819
Active Contributor
0 Kudos

Hello Karel

PRODUCT CATEGORY item should not have UOM ( item type = product category)

By mistake BUYER have selected a NORMAL (as a ITEM TYPE)

since material only will have UOM .

please mention here sample contract item details here to understand more .

Former Member
0 Kudos

Hi Muthu,

this might be the case. Please find below contract  details for line 10 and 20:

Item = 10/20

A = P

I = empty (NORMAL)

Material = empty

Mat. Grp. = 123456

Short Text = Example Item

Targ. Qty. = 0

Order Unit = PC/EA

Net Price = 1.00

Per = 1

Order Unit = PC/EA

Thank you.

former_member183819
Active Contributor
0 Kudos

Hello Karel

Item = 1

Item category = Product category

Mat. Grp. = 123456

Short Text = Example Item

Targ. value = 50000

-----------------------------------

ITEM =2

ITEM CATEGORY = NORMAL

ITEM NUMBER=2

PRODUCT ID = MATERIAL MASTER NUMBER ( INPUT YOU NEED INPUT OR SEARCH)

TARGET QTY OR TARGET VALUE = you can input

UOM = will pick up material master

price you need to enter which you negotiated with vendor

----------------------

Hope now you understand .

When you select NORMAL - you will get UOM

When you select PRODUCT CATEGORY - UOM will be diabled ( you can not input any values)

------------------

please make inactive and create a new item with appropriate data.

Muthu

Former Member
0 Kudos

We have involved SAP and they are currently looking into the code. I'll let you know.

Former Member
0 Kudos

One another possible work around is to implement the SOS BAdI and fetch all matching contracts in the source of supply list. The buyer can then select the appropriate contract line item(s) from the list.

As Muthu suggested, product category contracts would not have individual materials and therefore no UoM. If there is a manufacturer part number for the line items in the contract and you are referencing it in your shopping cart, then you can differentiate between the line items/materials.

I hope it helps. Else, please share what SAP says....

- JL

Answers (2)

Answers (2)

former_member183819
Active Contributor
0 Kudos

Hi

I have a question for you.

How the product category contract will have UOM?

did you create contract for NORMAL or Product category for item category ?

Muthu

Former Member
0 Kudos

Hi Muthu, the contract contains e.g. three positions. Each one with the same prod cat but with different UOM. My issue is that the first SC position will determine the correct contract item, but for all other SC items with different UOMs the contract item determined for the first SC item (with wrong UOM) appears. The contract data from the first iteration gets not refreshed when UOM changes. It actually does get refreshed when prod cat changes in SC items!

Thank you.

former_member183819
Active Contributor
0 Kudos

Hello karel

let me understand first on contract.

(1) What is the Item category for the line item of the contract i.e NORMAL or Product category?

NORMAL - only materials and it can have UOM

Product category - There is no UOM

first confirm this

or

BUYER created a contract as NORMAL for product category with UOM?

then we will go to shopping cart details for investigations.

Muthu

Former Member
0 Kudos

The contract has been created in backend with position type Standard (empty), material group, price and UOM - and without material number.

Thank you.

Former Member
0 Kudos

Note 1679066 - Same contract item in all items

has been implemented without success.

Former Member
0 Kudos

Hi Karel,

See if note 1491691 helps.

Regards,

Naveen

Former Member
0 Kudos

Hi Naveen,

the note 1491691 is valid up to SP8. We are on SRM_SERVER 700 SP11.

When debugging down in method SOS_VALIDATE it appears a structure (MT_CON_LIST) is not cleared for the actual iteration but still contains the determined contract items from the first iteration. I have no explanation for this.

Thank you.