Confirmations in the Classic Scenario

We are currently running SRM 4.0 and using the classic scenario to create reqs and POs in the backend system. We want to do GR in SRM and have setup the central receiver role. Is there an ALE process that needs to be activated to see the list of POs in SRM?

Hello Nancy,
Check whether you have done below config or not:
1. Creation of Partner Profile using tran WE20 for Message type ACC_GOODS_MOVEMENT & MBGMCR
2. Set up Ports under Transactional RFC using Transaction WE21.
You can also go through this SDN link:
Re: SC not to be seen in check status after MIGO in R/3
Regards,
Shiv

Similar Messages

Number of document created in th backend in the classic scenario?

Dear Experts,
Could you please tell me the number of document and its details created in the ECC backend in the below cases?
1. Case 1:
Define backend objects:Purchase requistion created if no stock available.
Is it correct that the system will create two documents here? The first document will be Purchase Requisition
( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
2. Case 2:
Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
Is it not a violation of standard classic scenario if only one document is created?
Thanks and regards,
Ranjan

Hi,
In other words in the shopping cart is approved
1) If the source is assigned -It will create a P.O in the backend (Classic)
2) If the source is NOT assigned -It will create a P.R in the backend (Classic) .. you have to assign a source
Regards
G.Ganesh Kumar

About the Classic scenario,ERP PO number didn't return go Shopping card

About the Classic scenario,We create a shopping card,And approved,the follow document purchaser order create the ERP system,But the Purchaser order number didn't return to the shopping card follow document tab page.How can help me?

Dear Masa ,
Yeah,we schedule program BBP_GET_STATUS_2 and CLEAN_REQREQ_UP,Then have this issue,We didn't know why.

R/3 Backend PO in SRM for Confirmation in Ext. classic scenario

Hi,
We are on SRM 4.0, Extended classic scenario
User created STO(Stock transport order) in backedn R/3(Not in SRM) and is visible in "Confirmation /GR services" in SRM.
But when user tries to do confirm it the items are not available and confirmation is not possible in SRM.
Is there anything missing in the system ? Please suggest
Best regards,
Sambit

it should be updated by running standard progarams which updated the status of the corresponding documents in R/3

PO Confirmation in SRM Classic Scenario

Hi,
I'd like to know if there's a functionality in SRM Classic Scenario wherein suppliers/vendors can tag POs that have been received by them?

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Automatically create a PO from a catalog buy in the classic SRM scenario

All,
We are on SRM SAPK-70207INSRMSRV classic scenario and R3 EHP6 FOR SAP ERP 6.0
When a shopping cart is created and approved from the MDM catalogue we get an automatic purchase requisition. currently the purchasers manually create the purchase order from that purchase requisition but we want to have an automatic purchase order for every all catalogue buy.
is this possible in the classic scenario ?
Can we also assign specific purchasers to these automatically created purchase orders, based on, for instance, the purchasing group as we use vendor invoice management so these purchasers will receive invoices with a price differences.
Thanks as ever.
Antoinette

Hello Antoinette,
A. Stork wrote:
is this possible in the classic scenario ?
Please have a look at below wiki:
Determination of the follow-on document type
A. Stork wrote:
Can we also assign specific purchasers to these automatically created purchase orders, based on, for instance, the purchasing group as we use vendor invoice management so these purchasers will receive invoices with a price differences.
Depending on product responsability and organizational responsability, purchasing group is automatically determined for each SC item.
For those purchasing groups, users are assigned inside the PPOSA_BBP transaction.
So, i do not understand your request.
Regards.
Laurent.

MM-SUS for the extended classic scenario

Hi,
I have done SUS-MM for the classic scenario.
Did anyone implement SUS-MM for the extended classic scenario ?
Did you face any problem or will it be same as 'classic' scenario ?
Please help
Thanks
Pranav

There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
Regards, IA

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

STO classic scenario SRM 4.0

Hi All,
We create SC that transferred to STO (Stock Transfer Order).
With the Classic Scenario(SRM 4.0) we use BBP_CREAT_PO_BACK.
A STO is created but the number of the STO is not displayed in SC.
Any suggestion ?
Thanks in Advance..
Moti

Hi Christophe
I) In CS - Did you use the scenario were a SC is transferred to a STO in R/3?
II) In ECS - Did you use the scenario were a SC is transferred to a PO in SRM and a STO in R/3?
Here are more detail of whate i have done:
A. In the Classic Scenario
I) Standard Purchse Order (this one works fine):-
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document from EC to NB,
2. Changing the Vendor from 1000000272 to 1000000271,
Run the program - CLEAN_REQREQ_UP.
The system as expected - A PO is created and
In the Follow-on Document, in the SC, I get tow messages:
1. Shopping Cart 1000000508/1 Follow-on Document Created
2. Purchase Order 4400002238/1
II) Stock transport Order (here the problem arises):-
In order to create a STO
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document type from EC to UB (STO),
2. Changing the Vendor to a Supplying Plant 236 (The central warehouse),
3. Changing the Item category 7 (U - Transport),
Run the program - CLEAN_REQREQ_UP.
A STO is created (Number 4400002239) but the number of the PO is not in
the SC.
In the Follow-on Document in the SC I get only onr tow message:
1. Shopping Cart 1000000511/1 Follow-on Document Created
To confirm the goods receipt of that STO from the status screen I get the messsge: 'PO 1 contains no items for confirmation'.
When confirming the goods receipt from the Confirm Goods/Service I get the message: 'PO 4400002239 contains no items for confirmation'.
B. In the Extended Classic Scenario
I adapted the BADI BBP_ECS_PO_OUT_BADI as follows :
Document type - UB (STO),
Supplying Plant 1000 (The central warehouse),
Item category 7 (U - Transport),
The BADI use the BAPI BAPI_PO_CREATE1.
The BAPI_PO_CREATE1 returns the following listed error messages:
'Net price must be greater than 0'.
Because the BAPI is activated whith extra parameters like: Invoice Receipt Indicator and Partial Invoice
Your help is appreciated.
Rgds
Yoram

Local contract and classic scenario

Hi all
A question regarding contracts - and interpretation...
On help.sap.com the following is stated:
<i>SAP Enterprise Buyer, as the central purchasing system, saves the contract data and uses it for local purchase orders and purchase orders of the extended classic scenario.</i>
I interpret this as, if one is using the classic scenario it's not possible to operate with local contracts in the SRM system. Can anyone confirm this?
And if so - any workarounds?
Our dilemma is that we have an extended classic scenario. Some materials are stock materials, and for these materials we are using a BAdi to switch off the extended classic scenario. No contract data is now added to the shopping cart, which I think is due to the classic scenario.
Thanks for your help in advance
;o)
Maria

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

SUS-MM integration in Classic Scenario for SRM

Hello All,
We are using SAP SRM in classic Scenario.
We also plan to integrate SUS with MM .
Looks like in the Classic Scenario with SRM , only the Direct material procurement is possible
using MM- SUS.
How would the SUS-MM integration work for Indirect PO's.
Our Process is as follows:
1) Shopping cart created in SRM for Indirect material & approved ( with cost assignment)
2) Classic PO created in backend & sent to SUS
After this step is it possible that the Vendor create the GR in SUS and it is sent to ECC for Approva through PI l??
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

Classic scenario using SRM SOCO

Dear Experts,
We use SRM7.0.
We want to use classic scenario u2013 creating backend PO and not SRM PO.
Can we use the SRM SOCO if we want to create backend PO ?
To clarify myself, can we implement this procurement process:
1. SRM SC
2. The SC will go to the SRM SOCO u2013 Sourcing cockpit
3. The purchaser will create backend PO from the SC items on the SOCO
Or in case we want backend PO, we must use ME57 on ECC system ?
Thanks and regards,
Lori

Hi Lori
It is possible to create a Purchase order in the backend from the SRM cockpit ( but it should not be order as Direct) by the Purchaser in the classic scenario.
Are you finding any difficulties ?
shopping cart create and ITS venture to cockpit upon sourcing configuration
add vendor and price in the shopping cart item or propose source of supply
and click PO creation and PO number will be generated from SRM system and PO will be avaiulable in ECC system .
BBP_CREATE_BE_PO_NEW - Purchase Order in Backend System
Using BusinessAdd-In BBP_CREATE_BE_PO_NEW you can change all the data thatis transferred to the backend system for generation of a purchase order. This includes, for example, the item data, the account assignment data, and texts.
All the shopping cart data is available as input parameters.
Ricardo / Lisa - please confirm the same when you read this thread and appreciate your comments here

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

Stock Procurement by Classic Scenario

Hi,
We are using SRM Server 5.5 as an add-on component to ECC 6.0. Only Classic deployment is in our scope.
Can anybody clarify me if we can procure Stock Material by Classic deployment of SRM?
While creating SC, when I click on 'Order as Direct Material' system is unable to determine the Purchasing Group and Org. So its unable to get replicated into R/3.
Thanks
Debashish

Hi Jagdish,
SAP told us that standard Classic scenario can't handle Stock procurement. For stock proc we need to have the extended classic scenario. In Extended classic we have Plan-driven procurement and we can do it there. Once again for stock procurement we need to define Local Purch grp and purch org and we need to have POs in SRM. POs in SRM is possible for Extended Classic scenario and this is not a part of Classic scenario.
SAP said that if we want to create Stock SC in SRM then we have to go for development.
Can anybody in this forum please confirm that in Classic Scenario we can't create a Stock SC (Without development)?
If you refer to OSS note 963000, it says that in ADD-ON SRM , only classic scenario is supported. If this is the case why I can see the 'Order as Direct Material' button.
Can anybody help me here??
Thanks
Debashish

What is external classic scenario?

Gurus,
What is external classic scenario? Is this the other name for Plan driven procurement OR something else? Please clarify
Thanks,
Sid

Hi Siddarth,
This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and a copy of the data is replicated to the backend system. Communication between Enterprise Buyer and the backend system is via RFC. The purchase order is created locally in Enterprise Buyer.
If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system. The plant is the criterion used for splitting shopping cart items into different purchase orders. This is because the purchasing organization is determined in the backend system based on he basis of the plant. Goods receipts (confirmations) and invoices can be pre-entered in Enterprise Buyer.
The following takes place in the Enterprise Buyer system:
Search for scource of supply, pricing, tax determination, commitments are updated in the backend system, account assignment and budget check are performed against the backend system.
Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the backend system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the backend system.
This scenario suits customers:
     Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buyer
     Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materials
     Who want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer
The extended classic scenario does not support purchase orders based on limit shopping carts or procurement card functions, as these require the invoice to be local.
Hope this helps you.
Please Reward Points if useful..
Regards,
Sreenivas

Confirmations in the Classic Scenario

Similar Messages

Maybe you are looking for