SRM table for backend PO & PR no. in Classic scenario

Hi All,
We are in classic scenario.
I need the table/view name which stores the PR and PO no. created in the backend system.
I could find different view names for PO,PR nos. from BBP_PD but is there any single table/view which stores this data ?
Any other table names will help.
regards,
Sambit

Muthu,
Appreciate your speedy response.
I found your answers helpful. Though the table didnt meet the requirement I have awarded you the points as it was helpful.
I'm not sure why but the BBP_PDBEI table should fetch the data when Bus. object type BUS2012 as suggested by you. But it only fetches the SRM POs created directly not the R/3 standard POs. I mean the table fetches "EBP PO" document type not the "R/3 PO" created directly in the R/3 backend system.
Thanks,
Sambit

Similar Messages

SAP SRM table for alternative approver

Dear all,
Can you please let me know which table in SAP SRM stores the alternative approver which is assigned in aprrover's inbox in SRM portal?
Regards
Arindam
Edited by: Arindam Ganguly on Oct 19, 2011 11:40 AM

Hi,
To see all the related tables for SC,goto trascn BBP_PD.
Enter the object typeas BUS2121(for SC).You will see the list of all SC's created in the system.Select any one and you can see the table(Header as well as item) names
Similarly you can see the tables for other documents which are created in the system like PO,Bid etc.
BR,
Disha.
Do reward points for useful answers.

SRM 5.0 Switching over from EC to Classic scenario

Hello Folks,
We are working in SRM 5.0 Extended classic scenario and the current need is to swipe from EC to the Classic scenario.
I thought it would be a click (uncheck Activation of the EC) and go. But to my surprise, system repeatedly is failing to transmit the Shopping cart into the back-end ECC 6.0 system.
Well...working into Vanilla SAP, my notion is there will be no need to activate any BAdis. Hence no BAdi implementation can be seen active in my system.
Please advice.
Thanks in anticipation.

Hi Marcin,
Thank you so much.
I awarded points for your help.
one quick issue, I am facing problem in posting invoice without reference to the PO. Error message was, "No logical system for FI is maintained. Inform system admin".
It sounds strange as I do have ECC as a solo back-end system. Second, I suppose I did best in assigning the logical system to ACS and SYS (PPOMA_BBP). Can you share your insight.
PS : I know it should be altogether a new thread. Be rest assured I will do all my best to reward your assistance !
Thanks.
Reg,

SRM table for messages

Hi,
I'm looking for the table in SRM wich contains the output messages with regard to Po's. I found that SRM does contain table NAST similair to R/3, however when I look into it, it isn't populated. The NAST table in R/3 only shows info for PO's that were created locally. I'm a BI consultant who is looking for the medium and date of PO output messages.
Greetz

Hi,
All messages you can find in the table T100 or in transaction SE91.
Rgs,
Pedro Marques

BAPI for replicate PO in Ext. Classic Scenario

Hello All,
What BAPI may i use to replicate PO in backend system?
please give me some hints
thanks
Paulica

Hi,
Try to BBP_PO_CREATE and BBP_PO_SAVE
Check this help too.
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
Regards,
Marcin Gajewski

POs are not available in Backend Ext Classic Scenario

Hi All,
Working with SRM 5 and Backend 4.6. in Extended Classic scenario.
For one plant the PO created in the SRM does not get replicated to the Backend whereas for other
Plants it happens.
Any body faced this before,pl give clues.
Thanks & Regards,
Nagarajan

Hi
(1)Is that PO in error in transfer?
(2)Hope you have defined local flag when your defined srm system.
(3) What about communication rfc users profile in both system.
(4) Hope RFC definition and logical system name are same/
BR
Muthu

SRM with PPS = Extended Classic Scenario

Does SRM Procurement for Public Sector (PPS) require Extended Classic Scenario? If so, could some one refer me to an official documentation that states such? Thanks.

http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements
PPS is only possible by ECS only.
Muthu

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

SUS / no goods receipt doc to backend in extended classic scenario?

Hello
have you any find a solution for problem
in SRM/SUS and goods receipt in extended classic scenario. Gr remains only in SRM not going to backend...
Brg Harri
Message was edited by: Harri Harkonen
Message was edited by: Harri Harkonen

Hi Christophe,
We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
The goods receipt is posted in backend this way.
Unfortunately we are not able to cancel or make a return delivery on this GR.
I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
Thanks in advance.
Rgds,
Martijn

Classic Scenario -Backend settings

Hi,
In the classic scenario the following is done in SRM
1. In the PPOMA_BBP - we are defining the Attribute : BSA - as EC
2. How this is linking with the Backend in SAP R/3.
We have created the Logical system-in SM59 and RFC are assigned to SRM and SAP R/3.
Backend SAP R/3
1. Number Ranges for P.O defined?
In SAP R/3 -SPRO -Define Document types -We can see the Type EC
How is the linking is achieved in SRM and Backend in classic scenario,.
Can you explain in details what are the setting done in SRM and SAP R/3 to achieve the Classic scenario
Regards
G.Ganesh Kumar

Hi,
Some of the basic settings around document types in SRM for the classic scenario which you have to define are the following :
In R/3 system:
1. define number range for the POs , PREQs and Reservations which will be created in R/3 system,
2. create document types for PO, PREQs and Reservations and assign to them the number of the number ranges created in step 1 - this is the doc type which you have to assign to BSA attribute
In SRM system:
1. define SRM transaction types
2. Define shopping cart number range, as well as the number range of the follow on documents created in R/3 system
3. Define number range for local confirmations of services and goods receipts
Regards,
Desislava

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

PO approval process in ECC for extended classic scenario

Hi All,
At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.
So our requirement is :
User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
Thanks in advance.
Regards,
Jennifer
Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

SRM table CFF_CONT question : huge table, what is that table for ?

Hello
We are looking to have more details about table CFF_CONT on a SRM system
The tolat size of DB is 344 GB
and only for table CFF_CONT we do have 284 GB, compared to total size this is really huge
the rest of the DB is only about 60 GB
What is that table for ?
Would it be normal to see that table on SRM growing much more than the others ?
Is that table something that can be clean up ?
Those questions are poping up becasue we are doing a system copy with sapisnt and R3load
and we see that this table only is requiring a so huge amount of thime to be exported
Regards

By the way ...
That CFF_CONT table belongs to cFolder components

SRM table for backend PO & PR no. in Classic scenario

Similar Messages

Maybe you are looking for