PO attachment transfer to ECC - Extended classic scenario

Hi all,
We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to ECC PO?Is this possible in ECS?If so,what are the steps?

HI Alexander,
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
I hope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

Similar Messages

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

Attachment transfer of PO from SRM to Back end for extended classic scenario

Hi Experts,
We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
Thanks ,
Aishwarya.M

As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario
http://scn.sap.com/thread/1873708
Also I suggest you should debug and see if its sending attachment from SRM if yes then
could be something missing at ECC side , To debug use this
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
Are you configuring this for the 1 st time or its an error which u encountered?
You must raise a NOte to SAP for the same till a solution is found .
This one is another which you can check ..
http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

Sharing attachment documents (e.g. for P.O.) in extended classic scenario

Dear SAP SRM gurus
in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0 as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
My customer wants to know if there is the possibility of not replicating them.
Any suggestions will be appreciated.
Many thanks in advance
Best regards
Gianluigi Brenna
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

Hello,
In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
Regards,
Prasanna

PO approval process in ECC for extended classic scenario

Hi All,
At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.
So our requirement is :
User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
Thanks in advance.
Regards,
Jennifer
Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

Transfer of SC into PO in Extended classic scenario

Hi
Can anybody provide me with the ABAP call stack ( I mean the program logic) on how the SC is converted to PO and transferred to the R/3 system in the case of extended classic scenario. I know that the SC after the approval process is over a method called "setrelease" of object bus2121 is executed. I tried to debug his method but could not found out the exact logic.
Thanks
sankar

Hi Sankar,
You will find the answer here :
https://forums.sdn.sap.com/click.jspa?searchID=59712&messageID=2679107
kind regards,
Yann

Can we use the Extended Classic Scenario with MM-SUS

HI, expert :
    In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You can't change it in MM system .
    So, in this situation ,I want to know the MM-SUS can be suitable or not ?The PO can transfer from ECC to SUS ?
   If I use the decoupled scenario ,which one I can select ?MM-SUS or EBP -sus ?
   BR !
Alex!

Hi Alex,
as noted by Bill, in MM-SUS is the extended classic not possible at all.
By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
"Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."
Regards,
Peter

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

Tolerance key DQ in extended Classic scenario give Backen error message

Dear all,
I am using SRM 7.0, SP 9
Extended Classic Scenario.
I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
I also set up the ECC tolerances:
- Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
- And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
And even with this set up I still get the error message
u201CBackend Purchase Order quantity exceeded by 1 EAu201D
when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
What Configuration am I missing?
Cheers
Ulrike

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

Tolerances in SRM extended classic scenario

Hi all,
I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
However, whenever we try to confirm more than PO quantity, we get an error message. PO Ordered quantity exceeded by 1 EA
It seems so that SRM has a double tolerance check
one in SRM against defined tolerance (via attribute TOG)
one in R/3 against the PO tolerance
Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have POs without a material master. Are there any possibilities to skip the PO tolerance check?
Thanks for your help,
Martina
Edited by: Martina A. on Jan 15, 2008 1:13 PM

Hi
Depending on the SRM version you are using, Please go through the links, which will definitely help ->
Condition Type SRM - ECC
Tolerance in SRM and ECC (BE R/3)
Tolerance
Re: SC Budget check without SAP Fund Mgmt
TOG parameter and tolerance checks better understanding
Setting EKPO-UNTTO with BAPI_PO_Create
Re: SRM: many confirmation for PO
Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
Do let me know.
Regards
- Atul

Automatic generate the PO in extend classic scenario

HI ,expert :
   I work in SRM7.0 and extend classic scenario.
requirement :
     The employee create SC manually .If the SC is complete ,the following document PO will generate automaticlly .And if the SC is incomplete ,the purchaser can do "carry out sourcing ",and transfer the SC to RFX .
Q1 :
    How can I set the "sourcing "-always carry out sourcing ,or nerver carry out sourcing ,Or carry out sourcing for item w/o SOS ?
Q2:
   IF the PO generate automaticlly ,Can I chage it in SRM ,OR I must change it in ECC system ?
BR
Alex

Hi Alex,
In the path shared above, you can specify the product category for which you want to enable sourcing under 'Category', in the source system please mention your ECC system and under sourcing you can choose various options available in the dropdown.
You can choose to have sourcing when source of supply is not assigned or you can carry out sourcing always or never.
Regards,
Nikhil

How to automatically attach document in PO - Extended Classic

Hi,
We are using the SRM 4.0 - extended classic scenario. We are creating the PO via sourcing (Manually converting SC into PO by assigning the Vendor).
In our scenario, the Terms and Conditions have to be attached to PO automatically (without User need to browse and upload them).
Is there a BAdI to attach the Document to the PO automatically.
Regards,
Rahul

Hello Pras,
Rahul is not trying to transfer attachments to R/3, but to create automaticaly an attachment for the PO.
Rahul, the smartform + CUF solution is the simplest and cheapest solution, and the less consumming in DB space (no physical document stored).
If you want to handle it via an attachment, you must code CHANGE or SAVE BADI to add an attachment at header level, is PO is created from transaction BBPSOCO01.
You would have to store this document in SRM KPRO, as a document model, and store its ID somewhere.
So when creating the new attachement, you can retrieve it and duplicate it.
Another approach, to avoid replicating N times the same document, is to handle the PO header CUF only, and interprete this CUF when editing the PO. In this edition step, you could then read model and add it in your PO output.
You could also just create a new attachment link without creating a new physical document by just linking the document model to your PO via an attachment link in BBP_PDATT. To do so, just add a new entry in attachment internal table in CHANGE BADI, using the LOIO Object ID.
For the last solutions, you will need some skills around document storage in SRM (LOIO, PHIO, KPRO...).
Rgds
Christophe

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

PO attachment transfer to ECC - Extended classic scenario

Similar Messages

Maybe you are looking for