on 04-10-2008 12:04 AM
Hello SRM folks,
We are on SRM Server 5.5 with ECC 6.0 classic scenario. We have external requirments ( Purchase requisition in ECC) coming to SRM sourcing. The issue I observed that they always come up with one purchasing group. We have mapped all the purchasing group in the PPOMA_BBP.
Any idea why the SC in sourcing always the same purchasing group.
Thanks,
Pradeep
Hello,
The default settings value for Purchasing group works in the following
way : the correct purchasing group is determined on the basis of the
product category. And this information you can find out in the
organizational responsibilty in the PPOMA_BBP
( i.e. which purchasing organizations can potentially procure for the
department user). Also in the product responsibility we maintain which
product category(s) the purchasing organization is responsible. And if
system finds several purchasing groups that are responsible for the same
department and the same product category it will take the first one in
the table. You can confirm this behavior by changing the product
category in the default setting and you will see that it automatically
adjust the correct purchaing groups.
I hope this informations answer your enquiry.
Thanks and Kind regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gaurav is right,
As per the standard system behaviour, while transferring external
requirements the system always does a new determination of the purchase
organization data in the SRM system.
The backend purchasing group value
is not part of the interface and it is not passed to the SRM system
along with the purchase requisition as per the standard design.
To change this behaviour
i.e. if you want the ECC PR to go to worklist of the purchaser maintained in ECC PR
you need to employ 2 BADIs
BBP_PGRP_ASSIGN_BADI
BBP_DOC_CHANGE_BADI
we have done it
BR
Dinesh
Hi Dinesh/Disha,
Thanks for your reply. Do I need to implement both (BBP_PGRP_ASSIGN_BADI
and BBP_DOC_CHANGE_BADI) Badi Or only BBP_DOC_CHANGE_BADI.
Since we have maintained the same code for purchasing org and group in SRM and ECC system. We want to change the SRM SC purchasing org and group based (Implement BBP_DOC_CHANGE_BADI and making RFC call to the backend and passing purchase requistion and get purchase org and group) on ECC purchase req purchasing org and grp. This will also enable ECC PR to go to worklist of the correct purchaser/purchasing group.
If you have done the same could you please share the sample implementation for the same.
Thanks,
Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Disha,
Thanks but the below sample code does not look for the purchasing org and group information in ECC based on purchase req. I am thinking to get the PR no in the ite`m table i.e.it_item-ext_demid will have the PR no.Then make an RFC call to R/3 to get the PR deatils like P org and Pgrp etc. And update the same in the SRM SC.
Could you please provide some details.
Thanks
Hi Pradeep,
Your approach is right.You need to make an RFC call to get the deatils for the PR.The links in my reply are for the sample code to be put in the SRM badi.But,yes if you need ECC specific data,you need to make an RFC call to ECC.You could use the FM "BAPI_REQUISITION_GETDETAIL" for that.
P.S. If you find the replies useful,remember to say THANKS in the SDN way!
BR,
Disha.
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.