Extended Classic- GOA to backend-SOS

Hi All,
We are working in extended classic scenario. SRM 5.0 with backend as ECC6.0. We want to distribute GOA as a contract to backend. Also, we want to use backend contract as a source of supply in shopping cart and then in PO. How can it be done? Is that possible to distibute GOA as a local contract in SRM and in backend too? I know in the standard system it can only be distributed to backend but is there any way of doing it? It is quite urgent. Every useful reply will be rewarded with full points.
Regards
Kapil

Hi Kapil,
Just a thought, you can upload the same contract from back end to SRM using a report BBP_CONTRACT_INITIAL_UPLOAD and can be used for procurement in SRM.
Rgds,
Teja

Similar Messages

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

SRM 7.0 extended classic - attachments to backend

Hi,
We are in SRM 7.0 and have a requirement to store SRM attachments in the backend ERP.
This is for the extended scenario going through Badi BBP_ECS_PO_OUT.
Has anyone got a solution for moving the attachments to the backend?
Kind regards,
Alexander

Hi,
The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
attachment transfer logic was only implemented in the Classic Scenario.
One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
BADI does (BBP_CREATE_BE_PO_NEW).
We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
1413792 Attachment deleted after changing purchase order
Ihope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

Difference between service procurement classic and extended classic?

I could you find any document for extended classic.
Could anybody help explain what is different between the 2 classics?
Thanks!

In the Extended Classic scenario, the entire procurement process takes place locally in EBP (SRM) and a copy of the data is replicated to the back-end system. In essence, this scenario is an extension of the Classic Scenario.
The purchase order in the back-end SAP system (ERP , R/3 System) is a read-only copy that enables goods receipt, service entry, and invoice verification in the back-end system. The back-end purchase order cannot be changed. If you wish to make any changes to the purchase order, you must do so in EBP i.e. SRM system. Once you save these changes, they are transferred to the back-end purchase order.
While in Classic Scenario , The PO is created in the backend ERP system once the SC is approved.
In brief , you can say while in extended classic scenario , the backend ERP system is a read only system and we do everything is EBP (SRM) system only. and in Classic Scenario , ERP system was used to generate the purchase orders.
Hope it clarifies and gives you a little visiblity on what is the difference between both.

GOA as SOS (Source Of Supply) in extended classic scenario

Hi,
I understand that when I create a SC in EBP, GOA can't be a SOS in "Extended Classic Scenario (SRM 5.0)". If I want to make GOA as SOS, how do I do it ?
I have searched the forums and found that the below BADIs can be used.
BBP_CTR_BE_CREATE
BBP_CTR_INIT_UP
BBP_CTR_MAIL_BADI
BBP_CTR_MASS_BADI
Now I am looking for someone who has done this scenario and please explain how did you do it ?
With regards,
Pranav

Hi,
I had a former project where I modified SRM standard source so that I can use GOA as source of supply in extended classic scenario. In Standard, as you know, SAP doesn't allow to use GOA as SOS in extended classic. In extended classic, we have to use local SRM contract as SOS. In my case, it was SRM 3.0.
Cheers.

Sourcing of GOA in Extended Classic Scenario

Hello all,
We are using the extended classic scenario with both Purchase Contracts and Global Outline agreements.
Is it possible to use the GOA in the back-end as a source of supply in the sourcing transaction in SRM? What setting do I have to use exactly?
Kind regards,
sander

Hi
Which SRM and R/3 versions are you using ?
I guess, the following threads will help.
Source determination in backend (R/3) for distributed contract i.e. GOA
Transaction For Creating GOA
Distribution of GOA in R/3
FM or BADI s' used to create a GOA
GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
Hope this will help.
Please reward full points, incase it suits your requirements.
Regards
- Atul

POR transferred into MM(Backend) system in Extended Classic Scenario

I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9
As we are successfully send PO from EBP to SUS.
Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
Please tell us, Provided Solution will be really appreaciated.
Thanks.
Regards,
Pawan Keshwani

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

Extended Classic Scenario does not create backend PO

We have SRM 5.0 SP 11 with ECC 6.0 backend (only one comp code, one plant and couple storage locations in the plant). I am configuring extended classic in there with the Org structure having Local Purchasing Org/ Local Purchasing Groups and the ECC Purchasing Org/ ECC Purchasing Groups.
It appears I am missing something; the system creates a Local PO just fine, however, dont see any signs of the system attempting to create a PO in the ECC system (no runtime errors or logs in either system).
In fact, my shopping cart does not show any value for Location (although the Org has the ECC location assigned to the user).
Any help is highly appreciated. Thx.
Raja

ECC 6.0 is ERP_2.0 and not R/3_4.70.
also check the resp org unit consistency with BBP_BP_OM_INTEGRATE
with the option all object types.
if I am not mistaken there are some FMs to push the copt again
like
BBP_PD_PO_transfer
(pl check the syntax... don't have system)
also check on "bachend prgp responcible" for yr ECS settings
also check the logic if you have implemented
BADI control ECS
BR
Dinesh

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

SRM 7.0 extended classic possible for multiple backends?

Hi all,
I know that SRM 7.0 can be set up for multiple backends in the classic scenario.
And i assume it is also possible to do so in the EXTENDED classic scenario.
Could somebody please confrim that this is possible?
Has somesone already set up this landscape and any recommendations, advice, hits, do's and dont's?
Cheers
Ulrike

Hi Ulrike,
SRM 7.0 supports ECS for multiple backends. We are using it now.

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

GOA + Local Contract distribution to R/3 in Extended Classic Scenario

Dear SRM Gurus,
System Information: SRM Server 5.5 EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ??? Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!!

Output from backend in extended classic

Hi Experts,
In extended classic scenario it is possible to sent the output from backend?
Does anyone know have to activate this, and how to deactivate the output control from SRM.
Proces as I want it:
- Creates a shopping cart in SRM.
- Creates a PO in SRM on behalf of the shopping cart, no output.
- The PO from SRM is replicated to R/3.
- The PO is sent to vendor fra R/3.
Best regards
Kim Oster

yes franz is correct. we can do this from consulting note which he mentioned.
PO Output messages for ECS PO's
br
muthu

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

Extended Classic- GOA to backend-SOS

Similar Messages

Maybe you are looking for