on 11-14-2007 1:27 PM
Hi,
We have the following config in PPOMA_BBP:
EBP Purchasing Org
External R3 Purchasing Org 1 - Company Code 1
External R3 Purchasing Org 2 - Company Code 2
All product categories, default purchasing org is set to the EBP Purchasing Org. The other external R3 orgs default to an external R3 channel specific to a plant & company code.
Sourcing is based on product category (buyer determination)
How do you set the shoppers default purchasing org in SRM?
Hi,
We have recently upgraded from SRM3.5 and we are on SRM 5.0.
We have both the extended classic & classic scenarios implemented together for our different company types:
Company 1 - R3 Backend 1 (Purch Org1)
Company 2 - R3 Backend 2 (Purch Org1)
Company 3 - SRM company (i.e no backend communication) (Purch Org1)
Company 4 - R3 Backend 1 (Purch Org2)
The issue comes in with the having 2 different company's on the same backend system, we have created a seperate purch org and assigned the same buyers to different purch groups to cater for this.
However, it is automatically defaulting to the Purch org1 for our company 4 shoppers. I have assigned and set all settings in the attributes and extended atrributes in PPOMA for the new company org unit to default to that companys'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same issue. We have a one-to-one relationship between purchasing organization (not purchasing group) and company code. We use the classic scenario. We use the same purchasing groups for both companies/purchasing organizations.
In the shopping cart, we would like the user to choose the company code and then have the purchasing organization automatically default (therefore, we can make the purchasing org field invisible on the shopping cart screen).
How did you resolve your issue? Can you send your code fix?
Bonnie Mohammadi
Sr IT Applications - IT Services
We Energies
office 414-221-2962
Hi,
The purchasing org is determined by the purchasing group.
On the other hand, which scenario you are deploying - classic and ext classic? Classic only backend group is allowed. Ext classic allows for both.
Hence you need to set which purchasing group is responsible for the shoppers and the org will be determined correctly.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
<b>Please provide some more inputs... Which SRM version are you using ?</b>
<u>Take help of ABAP person to use BADI in this case as an alternative approach ...</u>
<i>Use BBP_DOC_CHANGE BADI / BBP_PGRP_ASSIGN_BADI / BBP_PGRP_FIND</i>
<i>Use BAdI BBP_PGRP_FIND for purch.group determination</i>
<u>Default the values in Purch Org and Pur grp fields in Sourcing screen</u>
Do let me know.
Regards
- Atul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.