Plan-Driven in classic scenario

Hi there.
We are working with classic scenario in SRM 5.5
We are customizing plan-driven procurement (only MRP without PS and PM modules)
Is it possible the next flow?
For ECC system
1. MRP creates purchase requisition
2. We pass the purchase requisition from ECC to SRM as SC
For SRM system.
3. We create bid invitation and bids from the SC
4. We create a PO in classic scenario (in ECC)
We try to do it, but when the SC is created in SRM, always appears as extended scenario.
Moreover we have deactivated the extended scenario.
Is it possible to run Plan-Driven in classic scenario or it is mandatory extended scenario?
Thanks and regards.
Raúl.

Hi,
The document flow you mentioned is possible with classic scenario.(The SPRO setting "activate Extended Classic " is not checked).
You can have all PR's transferred form R/3 to SRM and create Bid invitations from the SC's created in SRM in Sourcing Application.
BR,
Disha.

Similar Messages

Plan-driven procument - ERP, EBP, SUS ?

Hi,
If we use plan-driven procurement, techincal scenario Classic should be used, then it's MM-SUS, current status is, "PR, convert PR into PO" all done in MM (ERP), then transfer to SUS, my question is, could I display and change these POs in EBP?
Regards
jack

Hello,
PDP scenario:
1. PR in ECC - Send to SRM for sourcing - RFx in SRM - PO in ECC
2. PO in ECC - Transfer to SUS
3. Change in PO in ECC - Transfer to SUS - Change displayed in SUS
Classic scenario : PO is created in ECC & doesnot exist in SRM, but PO will be transferred to SUS & vendor can view the changes.
Hope this heps.
Thanks
Ashutosh

PO type in classic scenario

Dear SAP gurus,
We're planning to use classic scenario in SRM 7 EHP 2 with backend ECC 6 EHP 5. In my previous project, i'm using extended classic, where after accepting RFx response, I can click simulate and create PO, and I can choose the PO type that I want to use (we have 5 PO types that we configure BOTH in SRM and ECC, as in extended classic, the leading PO is in SRM, I have setup internal number in SRM and external number in ECC).
In classic, can we also have the same feature where we can choose the PO type? Because as I recall, the determination of object in backend is in a setting where we can only define ONE number range for PO only. Is it possible during classic scenario I can choose which PO type that I want to create in ECC?
Appreciate your help on this.
Best regards,
John

Hi,
While creating PO from RFX, no pop up window will be opened to select the PO document type in Classic Scenario. Please have a look at the Knowledge base document no 1580116- "Classic scenario: Transaction types in Step 3 of the Sourcing Cockpit ".
SAP note 1323983 allows this modification. This is a modification note and is not available in standard.
Thanks,
Anshu

Reference to SC in classic Scenario

Dear SAP gurus,
We're planning to install SRM 7 EHP 2 with backend ECC 6 EHP 5. We plan to use classic scenario, as we know that now, classic scenario already support Sourcing Cockpit and creation of RFx/Auction referring to SC.
However we want to clarify somethings. As I know, the control for classic scenario can be set to 2 things:
a. If stock available create reservation,
b. If external, create PR if no source found.
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend. In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
Appreciate if someone can shed some light of system behaviour in this case.
Best regards,
John

Hi
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Ans: In classic scenario for a non stock item if the source is not there,after the SC is approved it will create PR
in the backend.
In Extended classic sceanario(ECS) if the Sc is not having source once the SC is approved it will go to Sourcing cockpit
(or) you can see in Purchaser worklist
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend.
Ans : In ECS if you creating Rfx to PO in the tracking tab you can see the SC.
In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
This is not clear
G.Ganesh Kumar

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

Is plan driven procurement possible in classic scenario

hai ,
is classic scenario possible in plan driven procurement? if possible anyone give me the steps required to do it.
thanks and best regards,
n.chakradhar

Hi there,
See the link to help
http://help.sap.com/saphelp_srm50/helpdata/en/18/8897267ef5eb44beb7fc578e95845e/frameset.htm
=====
Technical Scenarios
You can carry out procurement of external requirements in conjunction with the following technical scenarios of Enterprise Buyer:
·        Standalone scenario
·        Classic scenario
·        Extended classic scenario
=====
Regards,
Matthew

Self service procurement and plan driven procurement in classic scenario

hai friends,
i have configured self service procurement and now i am configuring plan driven procurement in classic scenario.my doubt is suppose a shopping cart is created and placed in a sourcing application of the professional buyer.And assume he accomplished sourcing activity and created purchase order .Now purchase order is created locally or in the backed.i am using classic scenario ,now can u tell where the purchase order is located? if i want to place that particular purchase order in SRM it self what will i do? thanks in advance.

Hi Chandra
before going to select Business scenario (self service, plan driven..etc), you must freeze the technical scenario. Depends upon your technical scenario, your PO will be created .
Where PO is created it is called leading system. It is SAP standard.
If you were selected Classic- Po created in R/3.- R/3 is a leading system .
if you were select ECS- > PO will created in SRM and Copy also will be created in R/3 system. In EBP only you can edit the PO not in r/3. here SRM is a Leading system.
regards
Muthu

Plan Driven Procurement in Classic scenario

Dear SAP gurus,
We are in SRM 7 EHP 1 with backend ECC 6 EHP 5. We are considering to use classic scenario, but we want to make sure that all the components are working fine. We have a scenario where MRP will be used in backend thus crearting a PR. We know that we can then push the PR to become SC in SRM then it can be processed there.
However seein note 505030 point 15, it seems that you cannot procure direct material using classic scenario. I assume that if using classic scenario, the PR of stock materials just wont go to SRM. However in other places I read that actually stock material works for classic scenario, but the PO will automatically switch to extended classic.
So which one is correct? Is:
1. For PDP and in classic environment, PR stock material NOT able to go to SRM, OR
2. For PDP and in classic environment, PR stock material can go to SRM, but when it is converted to PO it switch to extended classic.
Best regards,
John

Hi John,
The second option works in SRM.
Direct procurement in classic scenario works as if the system were extended classic. Thus your PO will be created in SRM and a copy of it will be replicated to ECC.
Regards,
Nikhil

Plan driven procurement issue in classic scenario

hi friends,
is it possible to replicate the external requirements from R3 to SRM in classic scenario .I tried to replicate the pr's from R3 to SRM.But i was unable to do it.kindly let me know the config steps required to replicate the PR from R3 to SRM sourcing cockpit.Thanks in advance
Thanks,
chakradhar

Hi,
Its certainly possible to replicate/transfer requisitions from ECC to SRM in classic scenario as mentioned by Dinesh.
Make sure the following entries and steps are implemented.
1. Entries in tables are necessary - V_T160PR and V_T160EX
2. Create SRM channel entry node in SRM organization structure and assign communication user (eg; RFC_USER) to the node. Node could be either a POrg or PGrp in the SRM root Organization.
3. Make sure the PRs from ECC are picked up by BBP_EXTREQ_TRANSFER BADI after approval or been released.
4. Make sure the PR requirement date and transfer date in BADI matches or use a variant for the BADI.
5. Check SMQ1 in ECC to see if the theres any Entry exists. Also check the EPRTRANS table to see if the PR still exists in table.
6. Check SLG1 in SRM to see if there are any issues in the transfer.
Once the its successfully tranfered, it will appear in Sourcing cockpit in SRM.
Let me know if you have questions.
Regards
SRM Consultant

Problems with PO creation in SRM in Plan Driven Scenario

Hi experts,
I have a problem with creation of PO from SC in SRM 5.0 (Extended Classic) in Plan Driven Scenario:
We transfer PM order from FI/LO (ECC 5.0) to SRM (the Extended Classic is activated).
SC (External req) is being approved
After approval there is a status on each SC position: "Item in transfer", after a long time status is being changed to "Error in transmition".
PO is not created and I don't know why. Any ideas?
Regards
RafaD

Hi RafaD,
Check for the shopping cart status message in BBP_PD.
Also check the status in application monitor using RZ20 then you will get a better picture about the problem.
Check the settings in the SPRO > IMG > SRM > SRM Server > Cross Application basic settings > Define objects in Back end systems.
Also check the following SAP notes which will help you in sorting out the problem :
Note 757625 - Incorrect Status I1112->analysis report
Note 1040878 - Cannot transfer shopping carts with status I1112
Note 631513 - Shopping cart in status 'Erroneous transfer' without alert
Note 1003350 - Follow-on doc BE PO not created for SC
Based on the error details you get through BBP_PD & RZ20, you can apply any of the relevant SAP notes mentioned above.
Hope this will solve your problem.
Let me know the outcome.
Rgds,
Teja

What technical scenario need for an Plan Driven?

Hello experts.
First of all; thanks four yours help and sorry for my english...
I want implant an Plan Driven with SRM 5.0 and ECC 6.0. My dude is the follow: what is the best technical scenario ? Classic or Classic extended ?
I explain a little:
1.- We don´t want makes Shopping cart in SRM.
2.- We bring the documents of ECC for Sourcing.
3.- We makes bids from Sourcing cockpit ( bbpsoco01 )
4.- We simulates that the vendor into the system to makes quots. we don´t want SUS.
5.- The contract are local in SRM but it´s replicated in ECC.
6.- PO are locals in ECC.
7.- Invoice and confimance goods / services in ECC.
I need helps please!
THANKS FOR ALL.
José Luis

Hi Jose,
I would recommend you to implement the Classic Scenario for a simple reason that you want the leading P.Os in ECC.
If you implement the classic scenario all your requirements get fulfilled except taht even contracts will be created in ECC but not in SRM.
Confirmation and invoice can be done in either ECC or SRM based on your convenience.
Hope this makes you more clear and helps in resolving your issue.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

I canu00B4t see de PR in the EPRTRANS Table in the scenario Plan Driven Procur

Hi,
We want to transfer PR from R/3 to SRM. We have customize the Plan driven Procurement, but we can´t see them in the EPRTRANS table. The Release Strategy has been completed in the PR.
Releases:
R/3 6.0, SRM 5.5
Any help please?

Hi John,
The second option works in SRM.
Direct procurement in classic scenario works as if the system were extended classic. Thus your PO will be created in SRM and a copy of it will be replicated to ECC.
Regards,
Nikhil

Invoicing Plan functionality in Extended Classic scenario

Hi,
For PO's are created in SRM-Extended Classic scenario, kindly let me know on how to maitain Invoicing plans.
Thanks,
KB

Hi. You could use ERS.
Let's say you wanted an invoice plan to pay every month for 12 months, you could create a cart on an ERS vendor and order quantity 12, unit months.
Then every month the user could do a goods receipt for 1 month.
That would trigger an ERS invoice, just like an invoice plan would.
The only problem with this is that you are relying on the user to do the goods receipt.
Regards,
Dave.

How to deactivate nterfaces triggering from ECC to SRM (Plan driven scenario)

Hi SRM Friends,
If I check in SXMB_Moni, I could see outbound interfaces which are triggering from from ECC to SRM.
Please guide me how to deactivate these XML messages.
We are not using EPRTRANS table, not maintaining V_T160 tables.
I don't know where to check further to deactivate this Plan driven scenario. Please suggest
Best Regards,
BV Babu

Dear Rahul,
Thanks very much for the reply.
Would like to inform you that we had to maintain an internal custom table entry to solve this issue.
This is related to a workflow issue. WF triggered unnecessarily... this caused triggered XMLs.
Regards,
Babu
Email : [email protected]

Plan Driven configuration in Classic

Hello Experts,
I am setting up PDP in Classic Scenario (SRM7.0/ECC6.0) and I have the following queries
1. I have created an entry channel in SRM org structure. Will this have any 'Function'? Should I assign an employee user under this node? Is this channel as good as a user department?
2. I want to use a different transaction type than SC for requirements coming from ECC. Should I copy SHC and create a new? Any settings to be done for this in ECC?
3. Should my employee user under the entry channel be an RFC user from ECC to SRM?
4. Where should I create a local purch grpu2026Can I create it under an existing purch org or should I create a new Purch Org also? This local purch grp will have the responsibilty for the entry channel.
Best Regards,
John

Please check below points:
1. Check tables table T160EX (for maintaining Material group, purch group & profile)and T160PR (maintaining profile and RFC connection). Make sure RFC connection entered here is working fine and connecting to SRM.
2. Check RFC connection to SRM and RFC user should be same as maintained in entry channel in SRM Org structure.
3. Check if entry BBP_EPRTRANS_MAINTAIN exists in ECC table TBE31. refer OSS note 656597 for further info.
4. Do you see any entry in SRM SMQ2 for this PR?
If everything above is fine then debug the FM BBP_EXTREQ_TRANSFER which calls BBP_BC_EXTREQ_INB on SRM side.
This function module calls BAPI_SCEC_CREATE.
Program BBP_EXTREQ_TRANSFER on backend side do the following:
- load a local stored copy of transfer table EPRTRANS
- create a package from the transfer table without breaks with one PR
- enqueue the corresponding EBAN entries
- transfer the package <-- in this perform we have BBP_BC_EXTREQ_INB and BAPI_SCEC_CREATE function module.
- dequeue the package.
Regards,
Jagadish

Plan-Driven in classic scenario

Similar Messages

Maybe you are looking for