on 2020 Aug 17 9:16 AM
Hello,
when you make a print preview of a PO in SRM (our release is SRM 7.0 EhP4), standard process determines Company Code based on Purchasing Group ID (check function module BBP_OUTPUT_COMPANY_FROM_EKGR).
Nevertheless, using this way, this means Company Organizational Unit's attribute COMPANY is inherited to Purchasing Organization, so to Purchasing Group too.
So, in case in your Organizational Structure, your Purchasing Organization is responsible for more than one Company Code (which means Organizationl Unit is not under Company Code), you will not have this inheritance.
Consequently, how is it possible to manage this situation by customizing?
If not, what is the SAP recommendation?
I writing this question in order to not have to open an OSS message. So if SAP employees can answer to my question, i will save time and SAP Support too.
Thank you for your support.
Regards.
Laurent.
Request clarification before answering.
Hello Gergo,
a solution i could consider is to assign my single Purchasing Organization to first Company code in the Organizational Structure.
This way, I would no longer have a raise in the BBP_OUTPUT_COMPANY_FROM_EKGR function module.
Nevertheless, i will have to redetermine Contact data in PO form (SF_PO-CONTACT) as i will always have data from same Company, whatever company code of SC Requester.
Regards.
Laurent.
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.