Extended Classic PO Replication Issue

We currently use the extended classic scenario for SRM 4.0 and ECC 5.0. After a recent system refresh purchase orders currently no longer replicate to the ECC system in our Q system. I've confirmed that the RFC destinations are set up as well as material groups and HR data replicated fine. Any help and ideas as to why POs are not replicating would be helpful.
PO changes are also not replicating from SRM to ECC.

Hi Chris
is refresh happpened only SRM system or r/3 system or both systems?
hope basis people done post refresh activities like running BDLS and attribute logical system changes.
make ensure that via SCC4 - for your clients (both r/3 and srm) logical system names are pointing to expected logical system not production logical system.
check sm59 connections? any rfc user has locked?
regards
muthu

Similar Messages

Extended Classic Scenario Pricing issue, can I over come by using SRM-MDM?.

Hi SRM GURU'S,
I am using ECC 6.0, SRM 5.5, SUS, LAC, cFolders and SRM-MDM with Extended Classic Scenario.
My Question is : In case of Extended classic scenario, there is issue with Pricing and conditions. Is there any possibility to overcome this issue by using SRM-MDM. Or do I have to go for IPC. My client has not brought IPC. I have to cover Pricing with the above components.
Anyone suggest me, how to proceed. Thanks in Advance. Awaiting for quick response.
Thanks & Regards,
John.

Hi Masa,
We can maintain Price and conditions as a record in CCM for Particular Material or Vendor. When you add that record to shopping cart it will update. I mean, If the provision is available in MDM, I don't want to use the Two components for same functionality.
If I use IPC, Is there separate license for that. What else need to be updated to use IPC (Patches etc).
If you have IPC configuration material, could you please share with me? How to bridge the SRM Conditions and ECC Conditions?
Please clearly give me details. I really appreciate you.
Regards,
John.

Extended Classic Scenario-Replication of Local PO to R/3 fails

Hi,
In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
Can anyone suggest if we are missing anything.
Regards
garugu

Hello,
this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
Rgds
Christophe

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

FM posting date issue in extended classic

We are experiencing issue with SRM deriving incorrect posting period when PO changes are made. We are in extended classic scenario with two FM periods open across fiscal years.
PO changes “No further confirmation” and “No further Invoice” from “No” to “Yes”, changes to anything on Account assignment(Asset, GL account, fund etc).
Earlier when we were in Classic scenario, we had FMOD capability to post the FM documents in previous year and current year. Do we have similar functionality retained in extended classic?

Hello Ratnakar,
could you please check below OSS note:
1981805 - Document Date is always updated with FM Posting Date
You could also check for OSS notes dealing with PSM-GPR-POR application area.
Regards.
Laurent.

Purchase order replication – extended classic scenario using XML proxy via PI

Hi Experts
Question:
In case of extended classic deployment is it possible to use XML proxy to
transfer SRM purchase orders to ECC? As we know as of SRM 7.01 its via RFC
whether SRM 7.02 onwards does SAP support XML for ECS too?
Has
anyone read about this in any of the SAP forums?
Background: In our project, client have invested
heavily on XI and XI monitoring and troubleshooting, integrated to SAP SOLMAN.
And would like to opt for XML mode of transfer and reuse existing solution.
This is the main reason we would like to be very clear in our understanding
before we go back to client.
We appreciate your time and support.
Regards
Prashanth

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

Extended Classic Scenario - PO Update issue

Hello experts.
We are working with SRM 5 in the extended classic scenario and we have a serious problem in a productive environment for the following case.
(01) We create a purchase requisition (PR) in R/3 with several items;
(02) We send PR to the SRM generating a shopping cart;
(03) The buyer creates a PO for all items from the shopping cart;
(04) The PO is transmitted to R/3;
(05) For some cases buyer changes the PO wich is sent back (updated) to R/3;
So far so good. The problem happens when some item in the request already has GR or Invoice. In those cases when the PO is updated on SRM, its transmission to R/3 does not occur, generating an error log that can be seen in transaction RZ20 of SRM.
I understand that if any GR or Invoice exists for the item it can no longer be modified, but is it expected that no other item can also be modified from SRM? What is the expected behavior for this case?
Moreover, even if the GR and Invoice have been canceled, we are still unable to update the PO in R/3 from SRM. Is this a expected behavior? It was our understanding that the PO should be updated if all incoming documents (GR, Invoice, SES ..) were completely canceled.
We appreciate any help on this matter.
Thanks and Regards,
Evandro Miasato

Hi, Masa,
Thank you for your advice,
I set the method U:Print Using Berkeley Protocol, after that
in trx. SP01 I have the Error Status on Composite Document -
Status Incorrect (Reason Unknown).
Best regards,
Guzal.

Shopping Cart replication using Extended Classic?

Dear Experts,
I was wondering if there is a BADI that I could possbily use to replicate SRM shopping carts to ECC Purchase Requisitions using the Extended Classic scenario.
Thanks in advance,
Mark

Hi Mark,
in case of extended classic scenario you can not create purchase requisition (the basic of this scenario, that you create at first the local PO, then this will be replicated into the backend system).
Therefore I would suggest to activate the BAdI BBP_EXTLOCALPO_BADI. With this BAdI you can choose between classic and extended classic scenario depending on your business logic (and create ECC PO or purchase requisition).
E.g. depending on the product category:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
clear: bbp_extpo_gl-bbpexpo,
          bbp_extpo_gl-mandt.
data: cat_guid type COMT_CATEGORY_GUID,
          category type COMT_CATEGORY.
cat_guid = ITEM_DATA-CATEGORY.
CALL FUNCTION 'COM_CATEGORY_READ'
    EXPORTING
      iv_category_guid = cat_guid
    IMPORTING
      es_category      = category
    EXCEPTIONS
      OTHERS           = 0.
if
* category XYZ
     category-CATEGORY_ID EQ 'XYZ'.
     bbp_extpo_gl-bbpexpo = 'X'.
     bbp_extpo_gl-mandt   = sy-mandt.
    return.
endif.
endmethod.
Regards,
Peter

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

Organization Structure Extended Classic

Hi,
Can you please help me with the following Questions
The below link says that one can use local porg and Local Pgrp in Extended classic. In this case when a PO is replicated to backend, system determined the back end porg for replicated PO based on Location or plant
http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/content.htm
a) My question is a plant can have several Purchasing Organizations assigned to it in back end ? In this case which one of them will be determined..
b) Also, if an SRM system is connected to multiple ECC. And similar categories are procured in all the ECC systems. We will have duplicate product categories after replication pointing to their individual ecc systems.
Now if we are to do Shopping carts using catalogues and since each catalogue item can have only one product category pointing to one of the systems.; this will result in duplication of catalogue items with each item for each system even though physically the item is same.
To avoid the above, If we decide to use local product categories and some how map them to one back end product category based on company code during creation of PO, it would help us simplify the process. Would it be Possible to do?
The purpose of the above question is. We want to use extended classic with plants and company codes mapped to back ends.
Entire Purchasing structure including Purchasing Organizations and purchasing groups will made local to SRM. The product categories are alos local product categories in SRM.
When i make the Shopping cart for example which is complete,
1. There should be some way to determine back end system. We are planning to use BBP_DETERMINE_LOGSYS. In this we will determine back end system using plant
2. Then the next question is what willl be the Purchasing org in replicated PO, Your clarification to "a" above will answer this question
3. the next thing is what will be the purchasing group in the replicated PO. We are planning to use BBP_PGRP_FIND to do this
4. The next thing is what will be the Product category in replicated to back end. Your clarification to "b" willl answer the question.
c. Finally because of this design, will we have issues with contracts etc......
Edited by: kiransap25 on Aug 3, 2010 8:35 PM

Hi Kiran,
Regarding your 1st question:
a) As it can happen in backend for plant associated with sevarl P orgs, but in SRM it is one to one and I think you can have a custome table in EBP for that one to one relationship through which you can decide the backend Pur Org in backend based on the plant.
b) Not very clear with the question, But the Product categories are based on the Backend and so is the catalogs which you assigned as in the users attributes which is get validated with the co code and backend system (based on the user attribute).
IS

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.

Error while changing PO in SRM extended classic Version 5.0

Hi Guys,
we are facing issue while changing PO in SRM , this is extended classic with version 5.0.
The system status is active() is error message and PO remains unchanged. Kindly help to resolve this issue. we have an approval for even PO if a user changes the qty in the PO then it calls the approval WF logic.
Thanks
Srujank

Hello Srujan,
Go through the following thread:
Re: PO status change
Hope it helps.
Thanks,
Neelima

PO error - extended classic scenario

Hi Guys,
I'm using SRM 5.0 with extended classic scenario...
During creation of the purchase order locally (in SRM) I got the "error in process" status.
My means of T-code RZ20 I got the following info to ithis error:
context:B2B Procurement
object name:Purchase Order
short name: Backend application errors
status: Active
Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
using Transaction BBP_PD I got the following status:
Status: I1080
Description: in transfer to execution system
Do you have any idea what should I do in order to resolve this outstanding issue?
many thanks in advance for your help.
regards,
Piotrek

Hi
Go to transaction - SPAM to get all the required Patch levels and other required system version details.
Meanwhile, try the following SAP OSS Notes as well ->
Note 508972 - Error during transfer of extended purchase orders
Note 881650 - Duplicate transfer/output of the purchase order
PO status in " error In Process ".
Error in Transfer Process (Urgent )
FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)
Hope this will help.
Regards
- Atul

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

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

Extended Classic PO Replication Issue

Similar Messages

Maybe you are looking for