PDP PM in classic mode?

[Former Member]

Hello All,

A new question for you all.

First our system status for ready ref:

SAP_ABA 700 0011 SAPKA70011 Cross-Application Component

SAP_BASIS 700 0011 SAPKB70011 SAP Basis Component

PI_BASIS 2005_1_700 0011 SAPKIPYJ7B PI_BASIS 2005_1_700

ST-PI 2005_1_700 0003 SAPKITLQI3 SAP Solution Tools Plug-In

SAP_BW 700 0010 SAPKW70010 SAP NetWeaver BI 7.0

SAP_AP 700 0007 SAPKNA7007 SAP Application Platform

SRM_PLUS 550 0007 SAPKIBK007 SRM_PLUS for mySAP SRM

SRM_SERVER 550 0007 SAPKIBKT07 SRM_SERVER

The business flow we are mapping in SRM:

- The strat purchaser creates Bid Invitation in SRM.

- He chooses bidders.

- The BI is published.

- The bidders register for BI and submit their bids.

- The strat purchaser compares different bids.

- Selects the winning bid and accepts it.

- The accepted bid is sent for approval.

- The approver checks and approves the bid.

- The strat purchaser process the BI again and clicks the "Create PO" button

in the change BI screen.

- Through BAPI the PO is created in ECC.

We are working in CLASSIC mode.

and for the above functionality there seems no problem in CLASSIC.

But now our customer says that , the strat purchaser will not make BI afresh in EBP.

He will create PR first in ECC.

Then this PR should be transferred to EBP

(can do with BBP_EXTREQ_TRANSFER).

This PR should come to strat purchaser's worklist.

He will procee this requirement and create BI out of it.

This is standard feature of PDP PM scenario.

But if we map this what I logically feel that SRM becomes leading system

and hence technical mode goes to EXTENDED CLASSIC.

Hence finally we will be compelled to make PO in SRM.

Which we don't want because we don't want to employ IPC for pricing.

I invite your comments on this requirement.

Can we process ECC PR in Strat purchaser's worklist and still be able to

create PO in ECC automatically?

BR

Dinesh

<b>Don't worry about the points.</b>

[Former Member · Accepted solution]

Hi Dinesh,

there is a yes and a no portion for your question:

- YES for pushed ECC Req which contain an account assignment.

These Reqs you use the push mechnism and source them in SRM with a classic PO

--> Standard Scenario "Procurement of External Requirements"

- NO for pushed ECC Reqs with material and no account assignment

These Reqs can be pushed up, nevertheless, by standard the system follows the extended classic scenario,

assigns the Req to the local POrg and local Pgroup and wants to create a local PO in SRM.

--> Standard Scenario "Plan Driven Procurement"

Without the extended classic, the PO fails in for this scenario in a classic environment.

In order to make it happen with classic, you need to program you own PO creation program.

A bit tricky as you need to cover a lot of stuff, but possible.

Thanks,

Claudia

[Former Member · Accepted solution]

Hello All,

Thanks.

Further.

If we activate ECS and after some time the client changes the business requirement , then will it be possible to come back to classic scenario?

Pl. give pros and cons and precautions.

BR

Dinesh

[Ramki · Accepted solution]

Hi Dinesh

I would advise this.

If you think, you need both Classic & ECS or there is a future possibility, do not activate.

Use the BADI to control extended classic scenario instead. It's a simple badi and gives great flexibility to you in the implementation.

Best regards

Ramki

[Former Member · Accepted solution]

Hi Ramki,

quick question:

Isn't the activation of ECS prerequisite for BADI BBP_ECS_PO_OUT_BADI?

Thanks,

Claudia

[yann_bouillut · Accepted solution]

Hi Claudia,

BBP_ECS_PO_OUT_BADI is used for ECS scenario.

When Ramki said use ecs badi, it deactivate the default ecs scenario for specific customer requirement to activate classic sceanrio for instance.

Kind regards,

Yann

[Ramki · Accepted solution]

Hi All

Let me clarify:

I was replying to query "If we activate ECS and after some time the client changes the business requirement , then will it be possible to come back to classic scenario?"

I was referring to BADI: BBP_EXTLOCALPO_BADI

You do not need to activate ECS Scenario but maintain the conditions (say Product categories) when ECS should be active.

If the conditions in this BADI are met, then ECS otherwise system treats the scenario as 'Classic'. Ofcourse other standard requirements shd be met (e.g. Account Assigned external reqmt etc) for classic scenario.

Best regards

Ramki

[Former Member · Accepted solution]

Hi Ramki,

thanks for clarify. I am still not sure if I understand right:

With BADI BBP_EXTLOCALPO_BADI it is possible to simulate the ECS without activating it?

Thanks again!

Claudia

[Former Member · Accepted solution]

Hello Experts,

Thanks.

(sorry....the higher points exhausted )

[Ramki · Accepted solution]

Yes. You are right.

You can use BBP_EXTLOCALPO_BADI for activating ECS (instead of the config option).

[Former Member]

Hi,

Atul has explained all the steps to be carried out in R/3 for transfer of external requirements to SRM.

The technical scenario in<b> your case will be extended classic with PO being created in R/3 backend</b> only.

For this you just need to do some basic settings for IDOC and maintainenceof the target backend system(i.e. ECC) for creation of PO(This is done thorugh BADI) ,details of which are given in the Strategic Sourcing Config guide.

So the purchaser will be able to process the PR from the Sourcing cockpit to create the BI,then view the submitted BIDS and then when the BID is awarded to a vendor,the Purchaser can execute the action "CREATE PO" after which the PO will be created in ECC(You will see the message with the PO number in SRM although the doc will be created in ECC).

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi

I have not tried this yet, but i guess it's possible to create PO in ECC automatically.

<u>Please ensure that following Settings are maintained in both SRM and R/3 systems.

These are Plan Driven Procurement - Prerequisites</u>

SRM system settings

-

---

-> perform all steps for direct material

-> set up entry channel for external requirements

-> assing an RFC user for this entry channel

-> assign your local purchasing group as responsible for this channel

-> set up sourcing configuration

R/3 Backend settings

-

---

-> maintain tables V_T160EX and V_T160PR

-> make sure to have a RFC connection to the EBP system, with the same RFC user as in the entry channel (with SAP_ALL and SAP_NEW Profiles)

-> schedule report BBP_EXTREQ_TRANSFER to transfer the requisitions to EBP

After customizing the direct material, there are additional steps necessary:

-> Using an entry channel, the requisitions are transferred into EBP. This channel must have at least one

entry user.

-> Corresponding to this entry user, you have to set up a RFC connection from back end to EBP by using

this special RFC user.

-> To get the requisitions in the work list for purchase orders, or in sourcing, there is a local purchasing

group required with the responsibility for the entry channel and the product category of the back-end

requisitions.

-> Customizing of sourcing or a BADI decides if the sourcing transaction or the work list for purchase

orders will be used

-> View V_T160EX in the R/3 back end determines which material groups and purchasing groups are

grouped into a profile. View V_T160PR determines which profile targets to which RFC connection.

-> The transfer itself is carried out by the report BBP_EXTREQ_TRANSFER. These can be scheduled (for example, once a day.)

The grouping of materials can be done based on a customer specific logic. Try the BADI - BBP_BADI_EXTREQ_OUT as well.

Have you seen OSS notes on this ? I remmember there is one OSS note which talks about the same.

Refer one useful link ->

Incase this does not helps, Please raise an OSS message with SAP.

Hope this will help.

Regards

- Atul