PR creation instead of PO in ECS scenario

We have a reqt that a PR be created from a SC if the SC exceeds a certain value. Which BADi can I use to facilitate this ?
We are using ECS scenario in SRM 5.0 and ECC 6.0.
Thanks
-Bakulesh

Hi Bakulesh,
If you are using ECS why do you want to create P.R again in back end system ?
You can very well use classic scenario which will create P.R / P.O in the back end as per the requirement and settings.
The setting in SPRO, Define objects in the abck end system is only useful in case of Classic scenario.
However by using BBP_EXTLOCALPO_BADI (Controlled Extended classic scenario) you can create P.R / P.O in the back end for the specific P.org and Product category combinations. This BADI overwrites the global Extended classic scenario settings.
Hope this makes you more clear. Clarifications are welcome.
Award points for suitable answers.
Rgds,
Teja

Similar Messages

MM-SUS-Invoice- ECS Scenario

Hi Experts,
We have a client requirement for activating SUS functionality. The main objective is Suppliers should able to check their own Invoice Statuses which are created and posted in back end R/3.
We are using Extended Classic Scenario (SRM4.0 and ECC6.0).
My Doubts: I have come to know through some of my friends and SDN forums:
1. To check Invoice status in SUS portal, the Invoice should have originated from SUS. Then only it is possible to check/find status from SUS portal.
2. In Extended Classic Scenario, it is not possible to replicate PO's from R/3 to SUS portal.
3. Is it part of SAP standard Scenario or purely custom development would be required.
If above 2 points are true, is there any alternate solution available for SUS usage for Invoices while using ECS scenario.
Kindly advice.
Regards,
Karnati

Hi Nikhil,
Thanks for your response.
In my scenario, All POs are available in R/3 irrespective of whether it is created and posted in R/3 or it is replicated from SRM/EBP (ECS Scenario).
For this sake, I would like to go for MM-SUS implementation.
My questions is:
1. Can I send all PO's from R/3 to SUS ( POs created in R/3 + POs replicated from EBP/SRM).
2. Can I get Invoice(Invoice with PO Reference) statuses to SUS, if Invoice is created and posted in R/3 with custom development.
3. Can I get Invoice(Non-PO Invoice) status to SUS, if Invoice is created and posted in R/3.
Kindly response and help to understand more about what SUS can and can not do.
Thanks,
Karnati

ECS scenario - Service PO and Service Entry sheets in backend

Hello,
We are on SRM_SERVER 550, SP07 and in the process of moving to ECS scenario.
There are some questions from me on the Service procurement in ECS.
1. When we create a PO with service item in SRM, will it get copied to backend as a Po with item category 'D'? This is how it happens in classic scenario,but does the same hold good in ECS?
2. When creating the confirmation for the service PO in SRM for ECS scenario, this would be a time entry/service entry sheet.
Would this be replicated to R/3 as a time entry sheet using RFC call?
Standard SRM210 guide mentions that goods confirmation will flow to backend as GR thro ALE/IDOCs and service confirmation will flow to backend as service entry sheets using RFC calls.
But I wanted a confirmation if this is entirely a standard SAP scenario or are there any restrictions on this?
Regards,
Srivatsan

HI,
Following are answers to some of your questions -
1) What do you mean by default unit measure? If this is the unit of Service, then you may change this in Service Master (T Code AC03). If the unit is at line item, then it should be AU, because you may order multiple services under one line each having different units of measure.
2) The message "No message record could be found for output of message. Save anyway?" is displayed because, you have not maintained output message for service entry sheet. Either define the output or remove the warning message at Attributes of system messages.
3) The process of service PO is same as material PO. The difference is that the item category for service PO is 'D' & then you maitain services for the line item either with or without service master. After completion of service, you create service entry sheet at transaction code ML81N & after accepting the service entry sheet, service entry sheet based GRN is prepared. The person who is posting MIRO is not required to know Service Entry Sheet number to post MIRO. The system automatically checks the service entry sheets accepted. Anyway, the service entry sheet number can be displayed at Purchase Order History tab of the conccerned PO at PO display option (T Code ME23N).
Hope your query is fulfilled.
Reward points if the answer is helpful.
Regards,
Prashant Kolhatkar

How to use Vendor Material Number in Purchase Order Creation - ECS Scenario

Hi SRM Gurus,
We are in Extended Classic Scenrio - SRM 5.0.
We want Vendor Material Number to be printed in the Purchase Order Layout. I remember in R/3 we have inforecord, wherein we have vendor Material number. Where do we maintain vendor material number in SRM. Suggest a suitable solution.
Thanks & Regards,
Ramkumar

Hi
Please refer to BBP_PD transaction to get the SRM Shopping cart (use Object type - BUS2121) / Local PO details (Use Object Type - BUS2201).
Please use the following useful links to refer in this case.
Re: PO Display
Vendor material no is not replicated in R/3
Re: PO Display
Re: SRM PO SMARTFORM
Re: SRM PO Print
Re: SRM PO SMARTFORMS
You need to copy the standard SAP smartform BBP_PO to a custom smartform say - ZBBP_PO.
SRM SPRO Configuartion Settings ->
In SPRO -> SRM-SRM server-Cross Application basic Settings ->Set output Actions and output format->Define Action for output document.
Select Action profile as BBP_PD_PO, click on processing type, choose smart form print or fax or e-mail as per your requirement and
change PO name as ZBBP_PO, in this case.
Incase you need any assitance, let me know.
Hope this will help.
Regards
- Atul

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

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

Reg SC convertion into PO in ECS scenario

Hi,
Why does the Shopping cart created in EB system with more around 19 line items show the status as Item in transfer process even though the entire approval workflow is complete?
There are no alerts found. Neither are there shortdumps.
The account assignment is of asset type.
The PO has not been created in the backend.
The function module to generate PO in the backend i.e. BBP_REQREQ_TRANSFER also does not convert the SC into PO.
Kindly guide as to what could be the reason for the same and the necessary corrective action required.
Thanks in Advance.
With Regards,
Rajesh

Hi Rajesh,
A basic doubt.
In yr title you have said yrs is a ECS.
In ECS the leading PO is to be made in EBP which is replicated in backend for ref and follow on docs.
Are you expecting that after SC approval the PO should be created auto in backend ?
In yr case it won't.
For that you need
classic scenario
and customizing setting
SRM IMG->SRM->SRM server ->cross applns->define objects in backend sys->PO if data complete
No ranges and trans types properly maintained
SC has a source assigned
BR
Dinesh

PCard Configuration In ECS Scenario

Dear Gurus,
Greetings for the day,
We are currently in between Development of Procurement Card (PCARD) Deployment in our customer landscape. They have SRM 5.0 version with Extended Classic Scenario (ECS)
We have performed below Configurations from SRM point of View:
- Configuration of Number Range for Procurement Card
- Define Card Company
- Allocate Company Code (Mapping of Back end Vendor, Clearing Account & Account Type)
- Define Blocking Reasons
- Manage Procurement Card Commitments
- Process Procurement Card
Also User Authorization Prospective we have completed below activities:
- Provide Procurement Card role (SAP_CRM_PAYMENT_CARD)
- Add Profile (M_BBP_PC) to respective user
- Maintain Parameter ID's (PCC & PCI)
- Maintain Authorization value as "4" while creating Procurement Card Master
Issue: When we tried to raise an "Describe Request" shopping cart with this user we are unable to see "Procurement Card" field in Shopping Cart "Basis Data" tab.
Also i am unable to find any option to maintain "Product Categories" option under "Procurement Card" node. So in case of SRM 5.0 scenario this option is not available? please advice
If any one has suggestions please advise.
Thanks & Regards,
Manish

Dear Experts,
Kindly help me to resolve above issue on SRM PCard Deplyoment
Thanks & Regards,
Manish

Remittance challan creation problem in Cross company code scenario.

I made to Advance payment to Cross comany code while posting time we deduct the TDS amount. at the time remiottance challan creation i got bellow error.please help to me
No unpaid tax lines exist for the given selection criteria.
Message no. 8I702
Diagnosis
The corresponding withholding tax line &1& is not present in WITH_ITEM table.
System Response
For withholding tax recovered from the vendor, tax line is present in table BSIS, but the corresponding entry is missing in table WITH_ITEM , which is necessary for challan updation. Check the entries.
Procedure
check entries in table WITH_ITEM for the open tax items chosen for clearing.
Edited by: TEEGALA SATISH on Jun 15, 2010 5:43 PM

Hi ...Actually i am getting same problem in challan creation.. Did you get any solution? ...

Follow on documents for SC in ECS scenario in SRM 5.0

Hi all,
We are on SRM 5.0,ECS.Is it possible that we can have the PO created,Invoice posted and then GR done in SRM?How is this sequence determined and what are the relevat settings to restrict this...i.e. I would like to have the PO done and then w/o GR,Finanance cannot post the invoice.
Also in terms of accounting,how much control is in SRM?
Thanks!

Hi
Try this
1. Do not have the GR based Invoice Indicator ticked on in the SRM Purchase Order
2. Then create an Invoice with reference to the Purchase Order.
This path is generally not recocmmended as you dont want your vendors to get payments unless they deliver goods to you. Try to sort out the issues with Goods recipients.
If its a Non PO stuff, then SAP Provides a non PO Invoice feature in SRM though...
Regards
Virender Singh

Suppress PO creation in local scenario

Hi all,
we are using SRM 5.0 in local scenario.
A requirement is to not create the PO after SC's approval workflow was run through successfully. This will be done later via XI.
Now, I tried to find a way to just stop after the approval workflow but could'nt find one.
Any ideas, suggestions?
Best Regards
Udo

Hello,
Could you check the foll cust link in SPRO:
Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).
PO is created if you set the "*" for EITHER the purchasing group OR the product category.
SRM is creating PR or PO depending on:
SRM customizing (ex: always external proc + PR if incomplete, PO if complete)
the interpretation of SC data by R/3.
IF your SC is considered complete by SRM (but with a fixed vendor and not a preferred vendor) the system will check if it can create a PO in R/3.
For this, each item will request a META_INTERPRETE_DATA to R/3, asking if it can create a PO. If R/3 considers this data as incomplete, it will reply to create a PR.
Usual cases of R/3 PR creation instead of PO:
prefered vendor in SRM (and not a fixed one)
custom checks in user exits in R/3
error messages in R/3 (ex: O6 334 In the case of a fixed vendor, please enter info record)
To debug without debuging into R/3, you can also try the following:
use BADI DETERMINE_TARGET_OBJECT and force PO creation
so the system will always try to create a PO
R/3 won't create the PO (for the same reason as in META_INTERPRETE_DATA), and will raise an error in SRM
finally you get the real error in application monitor (SC --> backend application errors
Related thread:
Re: PO not create from SC with source of supply in classic sena
Kind regards,
Gaurav
PLEASE GIVE FULL POINTS FOR USEFUL REPLIES

Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

PO creation in Classic scenario

Hi,
We have implemented classic sceanrio.
When ever I create a SC in SRM a PR is created in MM if the data is incomplrtr in SRM.
However, even if the data is complete in SC it creates PR in MM and not PO.As per the std functionality if SC is complete it should create PO in MM.
We have done the IMG settings as PO if data is complete else PR.
Please let me know what should I do to create PO in MM directly from the SC in SRM.
Thanks,
Manu

Hello,
Could you check the foll cust link in SPRO:
Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).
PO is created if you set the "*" for EITHER the purchasing group OR the product category.
SRM is creating PR or PO depending on:
SRM customizing (ex: always external proc + PR if incomplete, PO if complete)
the interpretation of SC data by R/3.
IF your SC is considered complete by SRM (but with a fixed vendor and not a preferred vendor) the system will check if it can create a PO in R/3.
For this, each item will request a META_INTERPRETE_DATA to R/3, asking if it can create a PO. If R/3 considers this data as incomplete, it will reply to create a PR.
Usual cases of R/3 PR creation instead of PO:
prefered vendor in SRM (and not a fixed one)
custom checks in user exits in R/3
error messages in R/3 (ex: O6 334 In the case of a fixed vendor, please enter info record)
To debug without debuging into R/3, you can also try the following:
use BADI DETERMINE_TARGET_OBJECT and force PO creation
so the system will always try to create a PO
R/3 won't create the PO (for the same reason as in META_INTERPRETE_DATA), and will raise an error in SRM
finally you get the real error in application monitor (SC --> backend application errors
Related thread:
Re: PO not create from SC with source of supply in classic sena
Kind regards,
Gaurav
PLEASE GIVE FULL POINTS FOR USEFUL REPLIES

Automatic creation of intercompany PO when creating a Sales Order

Hi Experts
Is there a standard way of triggering an intercompany PO when creating a sales order to the final customer (or the other way around, triggering a sales order to the end customer upon creation of an intercompany PO)? Scenario: business has setup a logistics company (company code X), which its purpose is to deliver goods to the final customer (home customers). However, sales orders are created from seperate chain of stores which belong to another company code (company code Y). This chain of stores have one sales organisation (since there is over 1000 stores under a chain). I need a way to represent that a sale originated from a store/plant belonging to company Y to end customer A. Also, I need a billing document (intercompany) from company code X to store/plant beloning to company Y.
Issues: in the intercompany config (assign intern customer numbers to sales org) - is there a way to assign a customer number at site/plant level so that when creating an intercompany billing it can be picked instead of the one assigned to the sales org and where can this be specified in the sales order (remember: in my scenario there are multiple stores/plants that belong to one sales organisation and it is not possible to use one customer number linked to the sales organisation.)
Desired results:
Sales order from store/plant YY belonging to company code Y to end customer A
Intercompany billing from plant XX belonging to company code X to store/plant YY
End customer billing from store/plant YY to end customer A
Thank you in advance for your help.

Hello Tsmash
I think you can acheive this with Regular Sales order + Inter Company STO combination.
Maintain customer numbers for each of the Plants from Company Y for the sales area belonging to Company X.
Then do the config for STO in MM using this menu path:
SPRO/Materials Management/Purchasing/Purchase Order/Set up Stock Transport Order
Here, in the activity 'Define Shipping Data for Plants', enter each of the plant-customers and the Sales area belonging to Comany code Y. Carry out other activities in this area appropriately.
Similarly set up Custom ( say Z1) Special Procurement type for Plant YY for stock transfer from XX using this menu path:
SPRO/Production/Material Requirements Planning/Master Data/Define Special Procurement Type:
Here maintain procurement type as F, Special procurement as U and plant as XX. You may need to repeat this config for each of the receiving plants (over 1000 stores under a chain) from co code Y.
In the material master MRP 2 for Plant YY, maintain procurement type as F and Special Procurement as Z1.
Sales order will be received under Co Code Y and sales area belonging to Y form customer A,
Because of the MRP config, a PO (STO) requirement will be raised on Co code X and plant XX. XX will send the goods to YY via a STO delivery using the Shipping data from 'Set up STO' config,
Plant YY will send the goods to A and bill that customer. Co Code X will raise an inter-comany bill on Co code Y.
That's how it should work. Try it and revert with any issues.

Contact person creation in SUS-SRM

Hello experts,
We are using SRM 5.0 (EBP and SUS).
At the moment we are using the Supplier Self Registration functionality, but would like to know if it's possible for the company to control the contact persons (users) creation, instead of the vendor to create them for themselves.
If so, how would this scenario work exactly?
Regards,
Gilberto Gallardo

There is possibility of replicating --> contact persons from SRM to SUS.
you have to use the transaction --->
BBP_SP_COMP_INI in SRM (EBP).
Please try to replicate the contact person ---> to SUS --> and see wether the same contact person can be used to login to SUS.
i have not tried this --> so not sure wether the user can login to SUS.
as far as i know , it is not possible for the purchasing company to create and control users on SUS.
this is because , supplier user needs to be connected to the supplier company -->
Edited by: khan voyalpad usman on Feb 7, 2008 12:45 AM

PR creation instead of PO in ECS scenario

Similar Messages

Maybe you are looking for