on 08-21-2006 1:15 PM
Hi SRM Experts,
The following is the process we can use in SUS scenarios.
1 Create a purchase requistion in r3 mm
2 create a purchase order with respect to purchase requisition in r3 mm
3 create a purcashe order response to the purchase order in SUS by the suppliers.
4 Create an ASN by suppliers intimating that the goods hae been supplied and are on the transit in SUS.
When an ASN is created in SUS it Automaticlly creates inbound delivery in R3.
5 Create a GR aginst ASN. in r3
6 create a invoice in R3 or SUS
Can all this be done in SRM with out a R/3? Need your views.
Any inputs that might throw more light on this topic would be of great help.
Thanks & Regards,
Jai Shankar.
Hi Jai shankar,
In SRM you have a flexibility for extended classic or classic scenario i.e.
1. Create a PR - this can happen in R/3 as well as EBP
2. Create a PO- this can happen in R/3 as well as EBP
3. Create a PO responce - this will happen in SUS only
4. Create an ASN - this will happen in SUS only
5. Create GR - this can happen in R/3 and EBP as well
6. Creat Invoice - this can happen in R/3 and EBP both
7. FI postings - this will happen in R/3 only
I have tried to give you total picture.
You need to understand the business requirements and system design for this
BR
Dinesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jai,
Again to give you total picture:
You can create an invoice in EBP (on behalf of vendor),
in SUS (supplier makes himself), in R/3 (on behalf of vendor as ERS evaluated receipt settlement).
When you make invoice in R/3-
Obiviously there is no need to transfer and invoice gets attached to PO or SA
When you make invoice in EBP-
Since EBP is considered as an internal system the connection is via BAPI and the invoice can be replicated in R/3 without XI
When you make invoice in SUS -
SUS being external system, by system design only accepts and generates XML message and to convert the same to IDOC .... XI becomes mandatory.
BR
Dinesh
(Helpful? pl. reward points)
Hi Jai,
As far as I know EBP is always a part of SRM Server and SUS is also a part of SRM server but SUS is specifically meant for External Vendors, so its keept in the same box of an SRM Server but treate as a seprate system for vendor and connected to EBP via XML only.
If it helps please award the point.
BR
Vijay Mittal
Jai
As per my understanding SUS can be used for PO responses, Invoice, etc in following 2 scenarios.
1. SUS with EBP in Extended classic scenario - In this PO will be resided in SRM system and SUS is integrated with SRM. PO response will be done in SUS and get updated in SRM PO.
2. SUS with bakend R/3 MM - In this PO resides in R/3 MM(may be Classic scenario where Po gets created in backend system or may be no EBP where procurement will be done in R/3 MM only). SUS will be integrated with MM and PO response will be done in SUS. Same will be updated in R/3 PO. In
Check your business scenario requirementa and decide accordingly.
PS : Reward points if it is helpful to you.
Regards
Jagadish
Hi all,
this sounds interesting.
I have a question concerning the Evaluated Receipt settlement (ERS) in EBP.
We are using Report BBPERS
Invoice is settled in SRM and be transfered to R/3 FI by IDOC (BBPIV01)
Besides that we are using the PPF (PostProcessingFramework) and we send an Email with the data of the credit note to the vendor.
Now we want to send a xml file with the data of the credit note as well to the vendor.
SRM Standard does not support this feature for ERS, am I right?
Any ideas how to implement this feature in the standard BBPERS report?
One idea could be
- distribute the standard IDOC BBPIV01 to the vendor as well (if it contains sufficient data)
Any other ideas?
Thanks
Regards
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.