How to "see" PO in EBP ?

[diegohs]

Hi everybody,

Right now, I can create a shopping cart in EBP and the a Purchase Requisition is created in R3. But now, I would like to see that Purch.Req. in EBP (Purchaser Role). If I logon as an operational purchaser, I can't see any document... =(

Any idea ?

I would really appreciate your help !

Regards,

Diego

[Former Member · Accepted solution]

Hi Diego,

it seems that you are running the so called 'classic scenario'. In this scenario, you will only have the information in the history of the shopping cart, that a Purch. Req. was created in the backend and you will see the number there. But the Purchase Requisition was created only in the backend. You would have to logon to your backend to access the PR.

In the extended classic scenario, you can transfer Purch. Requisitions from R/3 to your SRM, do the sourcing in SRM, create a local SRM PO and transfer this purchase order to your R/3.

Best regards,

Olaf

[diegohs · Accepted solution]

As always, thanks for your fast help guys!

What should I do in order to activate the extended classic scenario ?

1. I think I need to activate something in SPRO (Cross Application Basic Settings / Activate Classic Scenario

But I need something more ? something in badi's section maybe ? because I changed that but I can't see my PO's in EBP yet. =(

Thanks,

Diego

[Former Member · Accepted solution]

Hi,

To activate the extended classic scenario you have to:

-Manage locally a transaction type for local PO corresponding to the document Type for Extended POs in R/3

-Manage the attributes for this scenario (with local references for the local PO to be created)

-Activate the extended scenario either through SPRO or BADI

WARNING: Be careful, for this scenario to work, you have to make some custo (on R/3) or dev. (BADI in SRM) for Purch Org & purch group determination (see on OSS there is a note about that).

Regards.

Vadim

[diegohs · Accepted solution]

Hi Vadim,

let me see if I understand well this.

1. Go to spro and define number ranges for: "Define Number Range for Local Purchase Orders"

So, I should not have anything related with PO's in "Define Number Range for Shopping Carts and Follow-On Documents"

2. What do you mean about "manage" attributes for this scenario?

Regards,

Diego

[diegohs · Accepted solution]

Ok.. I did some configuration and now I'm having a problem. For some reason, the extended classic scenario uses only local Purch Org and Groups.

I found the note: 624172, which describes the options for solving this.

I chose this option, modify badi BBP_PGRP_FIND in order to able backend Purch Orgs & Groups.

Am I in the right line ?

Thanks for your help !

Diego

[diegohs · Accepted solution]

Guys, I'm stucked.

I want to enable the Extended Classic Scenario. Everything seems to go well except for 2 things:

1. During the Shopping Cart creation, when I try to select "Sources of Supply", it gives me records related to my LOCAL Purchase Group and LOCAL Purchase Org. Should I implement badi BBP_PGRP_FIND in order to fix this ? (I want to assign just my BE groups/orgs)

2. My Shopping Cart is approved and I dont have errors anywere. But I dont see my PO in any place nor any error. How can I debug this in order to check the problem's cause ?

Thanks for your help !

Regards from Mexico,

Diego

[Former Member · Accepted solution]

Hi Diego,

That is the point: for Extended classic scenario only local Purch Org and Purch Group have to be used, you wont be able to assign Backend Org to your document.

As described in the note you have either to fill in the backend codes in the PO transfer BADI, or to customize the backend (default purch Org on plant, and purch group on the RFC user).

So your problem now is to use the purchasing views of you suppliers defined in R/3 (that you can keep through the standard prg for vendor replication). There is no standard solution for that, but if you have only One purch org localy, you can assign your vendors to this org. in the replication program (see the selection screen). Another tool is transaction to copy purch views (I'll modify the thread later with the transaction)

Regards.

Vadim

[diegohs · Accepted solution]

Ok. the only thing I cant understand at all is the supplier config.

How can I assign a vendor to a Purch. Org ?

pd: In my vendor's attributes, I config the parameter BUK (Company Code): <MyBESystem>\<MyBECompanyCode>

Thanks Vadim!

Diego

[diegohs · Accepted solution]

Vadim,

Could you give me some advice about the implementation of badi BBP_PGRP_FIND ?

Thank you !

[Former Member · Accepted solution]

Hi Diego,

I answered in the other thread you've opened.

PS: Please don't forget to reward points to people who help you .....

Regards.

Vadim

[Former Member · Accepted solution]

Diego,

Please reward point for helpful answers.

Regards.

Vadim

[diegohs · Accepted solution]

Hi Vadim,

I already reward you 10 points for this thread ..

thank you !! 😃

[Former Member · Accepted solution]

You're right I'm so dumb :$ : bad reflex, sorry

[Former Member]

Hi Diego,

If you create PR in R3, that means you use the classic scenario.

In this scenario, you cannot access the backend documents (PR, PO or Reservation) from SRM, you only have light informations in the SC status.

To be able to manage purchasing documents in SRM, you have to implement the extended classic scenario in which a local PO is created and replicated in R/3 (not modificable in R/3).

Regards.

Vadim