cancel
Showing results for 
Search instead for 
Did you mean: 

Source determination in backend (R/3) for distributed contract i.e. GOA

Former Member
0 Kudos

Hi,

Source of supply is not getting picked up in R/3 in PR generated for Non- stock item while creating work order (IW31), though GOA exists in R/3 for that material. Maintaining source list also does not help. Any solution?

Thanks,

Manoj

Accepted Solutions (1)

Accepted Solutions (1)

former_member195032
Active Contributor
0 Kudos

Hi Manoj,

If you see in ME51n transaction ,there is a check box source determination,so if this is checked and you have contract ,you will get source of supply.

Now you are working from IW31,so you can ask some PM guys in team to help you out in this.I know one way which might work for you.

In SPRO->MM->Purchasing->Environment Data->Define Default value for Buyer.

See text maintained there..

Setting for Default value.

See any value which is maintained there.

by using display button.

See source determination tab as Create requistion check box.

attach this to paramter ID in profile maintained for user.

SPRO text.

In this step, you can change the standard settings of certain fields and functions for each user. You define individual default values and assign them to certain user master records.

You assign default values that you maintained in Customizing to a user by entering the key of the default value in the user master record under the parameter ID "EVO".

I feel this will solve your issue.,

regards,nishant

please reward if this helps

Answers (4)

Answers (4)

yann_bouillut
Active Contributor
0 Kudos

Hi,

I am not expert in PM...

However, did you already check the fllowing OSS notes ? :

843246 Source determination: Contract data is not transferred

910445 Determination of default values for non-stock materials

Kind regards,

Yann

Former Member
0 Kudos

Hi

<b>Please refer to following BADIs available in R/3 back-end system.

IWO1_ORDER_BADI

IWO1_PREQ_BADI

IWO1_WKCTR_CHANGE

WPS_CONNECTION

WOC_FL_DETERMINE

IWO1_SCREEN_MODIFY

MRO_CONTRACT

Also see customer Enhancements

exit_saplcoih_001

exit_saplcoih_002

exit_saplcoih_003

exit_saplcoih_004

exit_saplcoih_005

exit_saplcoih_006

exit_saplcoih_007

;

;;

until ...

exit_saplcoih_021

Also refer OSS Notes ->

551970

616699 </b>

Hope this will help.

Please reward suitable points.

Regards

- Atul

Former Member
0 Kudos

Thanks everyone, for the quick reply.

Nishant - The EVO parameter is already being used and it picks up source of supply when PR is created directly for GOA also.

Ramki - This is working fine for local contracts. Only GOA has this issue, when PR gets created through IW31.

Atul - BBP_SOS_BADI is not in R/3. Though it is available in SRM. The problem is with R/3 GOA.

Any other suggestion?

Thanks,

Manoj

Former Member
0 Kudos

Hi

Implement the BADI Definition in SE18 to handle the same.

<b>BBP_SOS_BADI</b>

<u>Note -> Please read the standard documentation of the BADI Definition before making any code changes.</u>

Hope this will help.

Please reward suitable points.

Regards

- Atul

Ramki
Active Contributor
0 Kudos

Hi Atul

Manoj's problem seems to be in R/3.

I am trying to find the reason for such a behaviour.

When a GOA is distributed to R/3, the R/3 contract behaves like any other R/3 contract.

Manoj: Can you pl create one contract directly in R/3 and see whether it is picked in Source determination ? Can you also let me know what are your steps for source determination ?

Best regards

Ramki