on 11-05-2009 3:24 AM
Hi Expert,
I'm working with SRM 7.0 Extended Classic Scenario (EHP3) assigned to backend ECC6. I have question related to enabling item hierarchy in Contract. I have activated Service Procurement in the configuration and all others configuration related to services which I could think of. However I could not create a contract with item hierarchy in SRM.
Our requirement to enable user to maintain a Contract with multiple single-level hierarchy, for example:
Contract ABC
1. Rates A
1.1 Sub item 1
1.2 Sub item 2
1.3 Sub item 3
2. Rates B
2.1 Sub item 1
2.2 Sub item 2
2.3 Sub item 3
Appreciate if you could shade some lights how I can enable the above structure in SRM7.0
Cheers,
Tom
Hi
Few points to be noted here:
1. Service hierachy functionality suppoted with EhP4
2. Business function LOG_MM_P2PSE_1 to be activated in back end
3. The service hierarchy scenario is like this: Service PR with hierarchy will be created in Back end and transfred to SRM sourcing cockpit. Then you can create create contract/RFx with corresponding service hiearchy items. As such you cannot create contract directly with hierarchy items.
4. For transfereing Service PR with hierarchy, you need to activate BADI - ME_REQ_SOURCING_CUST in back end
5. Appropriate PI service have to be activated to enable the transfer of docs through PI
Hope this clarifies you
Thanks
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran,
Understand on the process that PR with service hierarchy can be replicated from backend ERP to SRM and convert to Contract. However isn't it strange if the SRM Contract can support hierarchy items but doesn't allow user to create Contract with hierarchy directly. My problem is how is it possible to convert Contracts with service hierarchy currently in ERP into SRM - meaning ERP Contract to SRM Contract directly.
Please advise.
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sumat,
We manage to activate Outline item type enabling hierarchy to be manually created in Contract in SRM. However, we still have following issue transfer the Contract with items hierarchy to ERP (as per GOA distribution method). We discover the standard solution provided in SAP utilize IDoc to transfer GOA from SRM to ERP, and IDoc itself have limitation which unable to support item hierarchy. Hence, if we created a sample GOA with item hierarchy in SRM as follows:
Contract A
Item Item Type Description Qty Price
1 Outline Service Rate1
1.1 Service Service 1 1 10
1.2 Service Service 2 5 20
1.3 Service Service 3 1 30
2 Outline Service Rate2
2.1 Service Service 1 1 15
2.2 Service Service 2 5 25
2.3 Service Service 3 1 35
Once transfer over to ERP, the Contract is created as follows:
Contract A
Item Item Cat. Description Qty Price
1 Service Rate1
2 Service Rate2
3 D Services
3.1 Service 1 1 10
3.2 Service 2 5 20
3.3 Service 3 1 30
3.4 Service 1 1 15
3.5 Service 2 5 25
3.6 Service 3 1 35
As you can see the outline parent hierarchy link is broken from the sub-items maintained in GOA.
My question: Is it possible to transfer the SRM GOA to ERP in exact same hierarchy structure?
Cheers,
Tom
Hi Tom,
Now that you have achieved item hierarchies in SRM 7.0, to transfer the contract to SRM, you need to do the following:
Enhance the structure BBPS_CTR_ITEM on SRM side and BBPS_CTR_MM_ITEM on ERP side to include the hierachy information at item level and other data.
On SRM side, implement the BADI BBP_CTR_BE_CREATE method contract_interface_fill to fill the hierarchy data and enriching the data if needed.
Implement the BADI bbp_ctr->modify_idoc_data_ctr and rebuild the entire hierachy in ERP side. Ignore the item hierarchy built by standard SAP program.
Ensure that the BBP_CTR_ITEM_MAP in ERP is uptodate with the correct item mapping.
This should ensure that the hierarchy is transferred correctly in ERP.
Cheers!
Sumat
Hi Kiran,
The proposed setting has been done previously. Our scenario is ECS where SRM is leading - Contract is created in SRM and replicate back to ECC6. By having those settings mentioned there which work with external PR, and it should work for SC. I have tested SC with hierarchy but when I convert it to Contract via Sourcing cockpit, an errors occur "Enter at least one item" and an empty Contract is created. Additionally, we may also need to create Contract with hierarchy directly for data conversion.
Appreciate your response.
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran,
Contracts in SRM 7.0 do not support item hierarchy. Even if you manage to activate item hierarchy in contracts in SRM, you still need to write additional logic to transfer item hierarchy information to ERP.
The item hierarchy in SRM are delivered as a standard offering with SRM 7 Ehp1.
Best Regards
Sumat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.