on 04-23-2014 7:02 AM
Hi Friends,
I am a first times for Classic Scenario implementation.
Can the below scenario is a Possibility in SRM
1. SC creation
2. SOCO
3. RFX and Vendor Response
4. Central contract in SRM and distributed to MM
5. Release orders (PO) in MM with ref to Central COntract
I have few Questions:
1. What is the BSA attribute will be there in Classic
2. Can we create initiate sourcing from SC in CLassic or every time we create SC, it will create PR in ECC.
3. Can central contract be created locally in SRM and distributed in ECC (similar to Extended Classic)
Appreciate any help in this regard
IS
I am bit confused on the Scenario to Opt for (Between Classic and Ex Classic).
Follwoing Process are within Scope
Self Service Procurement
External PR for Sourcing in SRM (CPPR/Plan Driven)
Complete Sourcing (Startegic Sourcing/Bidding/Auction/)
Contract Management (Central Contract)
ROS
SuS (Supplier Collaboration)MM-SuS
SRM-MDM
Based on the Above, what will be the appropriate Scenario to go for.
Client is not specific about the System (SRM or ECC) for PO creation.
Regards
IS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1, For classic scenario, PO has to be created in MM side directly. Except for this, ther other scenario mentioned above area supported.
2, BSA attribute is used to define 'document type in R/3 system'. Here the value defined will be used for ECC documents which is created from SRM side. For example, if you create ECC PO from sourcing, the value defined here will be used for ECC PO type.
3, Can we create initiate sourcing from SC in CLassic? Yes.
4, Can central contract be created locally in SRM and distributed in ECC? Yes
Regards,
Ivy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks IVY for the reply.
I am bit confused on the Scenario to Opt for (Between Classic and Ex Classic).
Follwoing Process are within Scope
Self Service Procurement
External PR for Sourcing in SRM (CPPR/Plan Driven)
Complete Sourcing (Startegic Sourcing/Bidding/Auction/)
Contract Management (Central Contract)
ROS
SuS (Supplier Collaboration)MM-SuS
SRM-MDM
Based on the Above, what will be the appropriate Scenario to go for.
Client is not specific about the System (SRM or ECC) for PO creation.
Regards
IS
Hi Hayashi,
some customizing have to be done: such as sourcing should not be active for such product category, and in 'Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)', you should also define the backend object well. Meanwhile number range, etc should be defined well.
Regards,
Ivy
Hi Ivy,
In the SOCO, after creating PO draft there is no No transaction types available in SAP SRM.
I believe it is as per the KBA:1580116.
Howe the PO will be created and from where it will take the Tr Type.I have maintained the Tr type in both ECC and SRM with no range and making it External in ECC.
I came across the note 1323983. Will this help
Regards
IS
Hi,
note 1323989 is talking about creating PO from RFx, not sourcing. So it is not applicable for your case.
KBA note 1580116 is created by SOCO expert and she identified that what you are experiencing is standard behavior.
You have to define ECC PO type in SRM system too, and this type can also be set for attribute 'BSA' for the purchaser in ppoma_bbp. Then this type will be defaulted to PO type while creating ECC PO from sourcing.
Regards,
Ivy
Yes Ivy,
I did that and PO is created.
I am looking for the option to fill the requirement of multiple Tr Type.
For Example if my PO Tr type/Doc Type is based on Plants and user can procure for two plants.
So i'll assign the tr type in BSA (Multiple Tr Type).
Now How system will pick the correct one.
Is it some customization required here
Regards
IS
I am not sure as I have to test this in system but i found this some where which needs to be checked.
If there are multiple transaction types determined, then the default entry in the transaction type dropdown box is set to 'space'. If there is only one entry found for the user then this will be displayed as the default entry in the dropdown box. Here is the code section where it happens: /SAPSRM/CL_CH_WD_DOM_SOCO_GAF3, /SAPSRM/IF_CLL_MAPPER~REFRESH:
Hi Ivy,
I would like your view on the option to opt between CPPR or Plan Driven for the External Procurement.
I am planning to have thr PR directly in the SOCO and it will be manual to transfer. Not all PR from MRP is coming to SRM.
PR for Plant Maint. and service PR only
Will you be able to provide some insights between the two
Regards
IS
Hi IS,
For PR transfer, we only have report transfer or SOA transfer in PDP.
CPPR is another functionality which doesn't belong to PR transfer.
No matter you transfer PR via report or SOA, it can be transferred to SRM to generate SC.
If you want this SC to go to sourcing, you should configure customizing well in 'Define Sourcing for Product Categories', or use relevant BADI to set source_rel_ind indicator.
Regards,
Ivy
Hi Ivy,
Thanks for the reply.
My understanding is that CPPR:Collaborative Processing of Purchase Requisition (CPPR) is also From EHP4/ERP 6.0 requirements can be transferred using Collective Processing of Purchase Requisition (CPPR) .
Where as the PDP is the traditional way.
CPPR we need SOA where as PDP can be through RFC.
Do correct me here if i am wrong. I need to be clear in my understading please.
IS
Hi Ivy,
I require a help if you could to know if we can set up a PO approval Process in Classic Scenario.
I understand that , PO is not visible in SRM (PO not in BBP_PD) for classic scenario ,so not sure if the approval process can be set up and if the approver can see the PO and change it during approval.
Regards
IS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.