on 01-07-2013 3:32 PM
Hi guys,
i have a SC with 3 items. After the last step on the SRM workflow the framework splits the SC into 2 PO. Is there someone who can give me the attributes from SC which are responsible for the spliting?
I think i know these attributes:
All these attributes are identically on all 3 items except the category. The category has different content but all these categories points to the same purchase_org/purchase_group.
So i have no idea why the framework splits these SC into 2 PO !?
Thanks for feedback and hints.
With best regards
--Bernward Henkel
Please refer Note 1380879 - FAQ: Split criteria in the Sourcing Cockpit
Also you can look into methods
DETERMINE_BACKEND_OBJECTS
DETERMINE_LOCAL_OBJECTS of class CL_BBP_SC_TRANSFER for the split criteria.
Regards,
Sushil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sushil,
is there a difference between the the classic Scenario and the extended classic scenario ?
We have SRM 7.0 EC with 3 different backend systems but although if i have an SC for only one backend an for all items the same vendor, finacial system etc. the framework splits the SC.
I although testet the hierarchy of the items and the different categories of each item... but no idea what's going wrong !
Thanks for feedback
Regards
--Bernward
Hello,
There are some differences in split criteria for classic and extended classic.
For classic:
Class CL_BBP_SC_TRANSFER
Method SPLIT_BACKEND_PO
IF ls_object_split-fixed_vend <> <object_split>-fixed_vend OR
ls_object_split-proc_org_ot <> <object_split>-proc_org_ot OR
ls_object_split-proc_org_id <> <object_split>-proc_org_id OR
ls_object_split-proc_group_ot <> <object_split>-proc_group_ot OR
ls_object_split-proc_group_id <> <object_split>-proc_group_id OR
ls_object_split-agreement <> <object_split>-agreement OR
ls_object_split-be_doc_type <> <object_split>-be_doc_type OR
ls_object_split-be_co_code <> <object_split>-be_co_code OR
ls_object_split-ctr_hdr_number <> <object_split>-ctr_hdr_number OR
ls_object_split-plant_country <> <object_split>-plant_country.
For extended classic:
Method SPLIT_PO_LOC_CMP_CRITERIA
IF is_object1-guid_ven <> is_object2-guid_ven OR
is_object1-guid_prpven <> is_object2-guid_prpven OR
is_object1-proc_org_id <> is_object2-proc_org_id OR
is_object1-proc_group_id <> is_object2-proc_group_id OR
is_object1-pcnum <> is_object2-pcnum OR
is_object1-pcins <> is_object2-pcins OR
is_object1-subtype <> is_object2-subtype OR
is_object1-be_co_code <> is_object2-be_co_code OR
is_object1-ext_dem_logsys <> is_object2-ext_dem_logsys OR
is_object1-doc_type <> is_object2-doc_type OR
is_object1-logsys_fi <> is_object2-logsys_fi.
Also, in extended classic, if no vendor is informed for items, they will be split in different POs.
Regards,
Ricardo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.