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

Similar Messages

Technical Scenario Switch: From Standalone To Extended Classic

Hello,
Currently we are preparing the system to change the technical scenario from standalone to extended classic (SRM 4.0)
While the Customizing steps are clear, it isn´t so clear how the data that already exist in the system will behave after the scenario switch.
Before the scenario switch, the purchasing department is closing all open SRM local purchase orders.
Someone has already done this kind of scenario switch?
What were the problems you encounter?
Regards.

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Do let me know.
Regards
- Atul

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

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

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

PO Output in ERP for Extended Classic Scenario

Hi!
We have ECS up and running and now we would like to transfer PO to SUS, but not from EBP system. We would like to do this from ERP system because ASN creation from SUS functionality is really needed for us.
So, we have configured ERP system for message output (for message type NEU), but when PO is created in ERP system output is not created.
Could you please help me to solve this isssue?
Thanks and Regards,
Siarhei

Hi,
Which SRM version are you working on??
There is a Consulting note 883693 might help - we use it to allow EDI output of our catalog POs in R/3.
The note 883693 in which the steps are explained to use R/3 output when using ECS, however this is only valid for SRM 4.0 (SRM_SERVER 5.0).So it wont be helpful for you if you are on release SRM 5.0.
Another workaround would be to implement the BADI BBP_PO_INBOUND_BADI in ECC.In ECC BAdi BBP_PO_INBOUND_BADI, method BBP_MAP_BEFORE_BAPI ,you and write custom code to generate output for SRM copy PO .
Hope this helps .
BR,
Disha.
Do reward points for useful answers.

SRM PO failing to replicate to SAP backend in extended classic

Hi Friends,
Please can someone shed some light to this issue as the RZ20 log is not providing any answers!
We have created a multiline order and it has the status 'error in process'. For this reason the PO failed to replicate to SAP backend. The RZ20 log gives message:
PO 3000008888: No instance of object type PurchaseOrder has been created. External reference:
PurchOrder 3000008888: Document contains no items
PurchOrder 3000008888: Item 00003 does not exist
PO 3000008888: No instance of object type PurchaseOrder has been created. External reference:
PurchOrder 3000008888: Document contains no items
PurchOrder 3000008888: Item 00003 does not exist
Any help would be a appreciated.
Thanks again
Steve Walsh.

Hello Steve,
I guess error messages come from R/3.
Depending on your R/3 version, check by debugging in SRM functional modul driver (B46B_DPO_TRANSFER, B470_DPO_TRANSFER, etc.) what's happened with PO data between SRM and R/3.
Check also BAdI to modify backend data : maybe some wrong item data cleaning are done.
On the R/3 side, look for the where-used R/3 messages you have in your monitoring : you will be able to know exactly why you have those errors
Regards.
Laurent.

Caching Output from backend drivers

Hi,
I am noticing in the trace file that much time is consumed with the following trace note while sending reports to networked printers.
DST 51103 (rwfdt: rwfdtprint) CachingOutput from the backend drivers.
I am running oracle 10g release 2 on windows 2003 server platform.
Any thoughts?
Thank u.

Hi,
I am noticing in the trace file that much time is consumed with the following trace note while sending reports to networked printers.
DST 51103 (rwfdt: rwfdtprint) CachingOutput from the backend drivers.
I am running oracle 10g release 2 on windows 2003 server platform.
Any thoughts?
Thank u.

PO replication to R/3 from EBP in Extended classic scenarion

Hi All,
We are using ECS for plan driven procurement and bidding engine in our system.presently we have configured the system in sand box.We can able to do the entire cycle like PR transfer from R/3 to Sourcing cockpit upto PO creation in SRM.But PO's are not replicating to R/3. can any body suggest what may the problem for PO replication to R/3.
Thanks in advance.
Nanaji

refer to this link
PO send to R/3
Besides that please check the WF log for WS14000077.
Regards,
IA

SRM PO replication to backend ECC (Extended Classic Scenario)

I would like to have inputs on this scenario, as which BADI we need to use and what we need to do exactly to replicate PO from SRM 5.5 to ECC 6.0.
Thanx and Regards

Hi,
just try out the following:
If you activate the BAdi, make sure to take over all Import params into your Export params!
Otherwise data may be lost!
Here is an example:
*-- data declaration
Data: wa_longext like line of ct_longtextt,
          wa_item like line of et_item,
          zw_index type sy-index,
          zw_counter type ec_counter.
*-- take over all import data to exp params
es_header = is_header.
et_item[] = it_item[].
et_partner[] = it_partner[].
et_account [] = it_account[].
et_orgdata[] = it_orgdata[].
*-- Change data
*-- modify given vendor longtexts (ITXT) for example with a standard text
*-- for all positions
clear zw_index.
Loop at ct_longtext into wa_longtext.
zw_index = zw_index + 1.
if wa_longtext-tdid eq 'ITXT' ." Vendor Text
wa_longtext-tdline = 'Here your Text'.
modify ct_longtext from wa_longtext index zw_index.
endif.
endloop.
*-- or if you would like to add a line of text to a position
*-- loop over positions and read text for vendor text
loop at et_item into wa_item.
clear zw_counter.
loop at ct_longtext into wa_longtext
where guid = wa_item-guid
and     tdid = 'ITXT'
and tdspras = '???'." -> your language (E= English, D= German...)
endloop.
*-- if position contains vendor texts already, you know the counter index
*-- add 1 to counter to get the "new" index for your new line
zw_counter = wa_longtext-counter + 1.
wa_longtext-guid = wa_item-guid. "to combine the text with the SC position
wa_longtext-tdid = 'ITXT'.
wa_longtext-tdspras = '??'.
wa_longtext-counter = zw_counter.
wa_longtext-tdline = 'Your Text'.
append wa_longtext to ct_longtext.
endloop.
This is just an example which I have coded right now.
Hopefully without any syntax errors.
Of course you have to adopt this coding to your requirements.
Best regards
Andreas

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

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

PO Output in Extended Classic using 3rd party

Hi All,
Would really appreciate if anyone can pls help us out.
We are on SRM 5.0 in extended classic scenario. The client wants to output the PO to some of the vendors in XML but they don't have either XI or BC.
The questions is -
a) Is it possible to send PO to the vendor in SRM in XML without XI or BC.
b)If possible to send PO without XI or BC (The client currently have a 3rd party tool which converts the PO from R/3 to EDI format.).what are the special config required in SRM.
Thanks in advance.
Jay

Hi,
See these related threads:
Re: PO to Vendors
Output Purchase Order from SRM / EBP as File (without XI)
Re: Exporting PO from standalone
Re: SRM 4.0 Send PO to XI
Re: How to define a new "send medium" for a vendor?
Re: PO format (smartform): PDF vs HTML ?
Purchase orders output format.
Re: Data transfer from EBP to external systems
Re: Replicating PO from non-SAP backend to SRM
Re: Data transfer from EBP to external systems
related links:
http://help.sap.com/saphelp_srm50/helpdata/en/84/0783f35c1e11d2b403006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
BR,
Disha.
Pls reward points for useful answers.

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.

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

Output from backend in extended classic

Similar Messages

Maybe you are looking for