How to close extended classic PO in ECC...

Hi Friends...
We are in SRM 7.02 and ECC 6.05 in Extended Classic Scenario. One PO had been created for 1 Quantity 3 years ago. There was no GR/IR document posted against that PO. Now that PO had been archieved from SRM. But still PO is available in ECC with open quantity and also its appearing in the open PO report. Now requester wanted, the PO to be closed in ECC and shouldnot appear in the open PO list.
How to handle this situation.. How to close the extended classic PO in ECC at this scenario. As PO not available in SRM, we can not do anything from SRM side.
Your inputs are appreciated....
Regards
Sivakumar Kandasamy

Hi Sivakumar,
If you mean how to archive PO in MM side, please refer to the following info:
====
In ECC system, if you want to archive a MM PO, please use transaction
SARA->archive object MM_EKKO.
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
====
If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
refer to the following test data:
Parameters:    PURCHASEORDER      = XXXXXXXXX
Parameters:    POITEM
PO_ITEM                        = 00010
DELETE_IND                     = X
Parameters:    POITEMX
PO_ITEM                        = 00010
PO_ITEMX                       = X
DELETE_IND                     = X
You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
Regards,
Ivy

Similar Messages

Documents / Cookbook on how to configure Extended Classic Scenario?

We currently have the Classic scenario and are thinking of changing to exteded classic becuase we want to use the sourcing cockpit in SRM 7.0. Does anyone have any good documentation on how to configured Extended Classic?

Hi Sivakumar,
If you mean how to archive PO in MM side, please refer to the following info:
====
In ECC system, if you want to archive a MM PO, please use transaction
SARA->archive object MM_EKKO.
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
====
If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
refer to the following test data:
Parameters:    PURCHASEORDER      = XXXXXXXXX
Parameters:    POITEM
PO_ITEM                        = 00010
DELETE_IND                     = X
Parameters:    POITEMX
PO_ITEM                        = 00010
PO_ITEMX                       = X
DELETE_IND                     = X
You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
Regards,
Ivy

How to close extender tray on Envy 5640?

Just acquired this new today, and can't find any information about how to close the tray. It popped out automatically for the first printing job, and even when I fiddled with the paper loading tray etc when unpacking and it was switched off, but how should I close it? Do I just force it shut? I did this once but it seems very stiff and I don't wish to damage anything.
It doesn't auto-retract when switching off, and I don't wish to leave it open when not required because it is too exposed and risks being damaged.

Hey there,
There was no resistance as all when I pushed the extender tray back in, it slid back in nice and smoothly. If the tray is in the "unlock" position and it's still giving you resistance, perhaps there is a problem with your tray. Give us a call directly to report the problem with the tray and see if a replacement is required.
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region. http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

How to findout for which product category extended classic is activated?

Dear experts,
How to find out for which product category extended classic is activated? I am working in a test system. In spro settings, Cross aplication basic settings -> activate extended classic is unticked.
I see, the system allows me to create a Extended classic PO against a product category 001.
The product category has same ECC backend system as target and source system.
Is there any BADI implementation?
regards,
Ranjan

Hi
ECS - flag activated - means Extended classic scenario.
target determine badi - helps to create a PO in desired place.
source system and tatget system logical entry sjhown means
PRODUCT CATEGORY - created in Backend system and follow on docuemnts also created in ECC system - so it could be Classic .
as jay said determine log system badi used for DECOUPLE scenario ( Classic as well as ECS) .
some times unless we study the system in depth, hart to findout what is exact techniacl scenario.
or you can find out what type of POs are in BBP_PD for all PO means ECS.
This SRM tools can be used for many purposes.
some customers uses for Supplier registration only,
some one is using for only Bid invitation and Bid and selecting the vendor only
some one use for all non stock procurment only.
some one use for only free text - ....
taste vary in all business.
you must give more details like what are the Business docuement s are created in SRM
Muthu

Extended Classic Scenario - how does the integration work ?

Hi,
Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?
Many thanks,
fiona

Hi Olaf,
I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
The Extended classic scenario only refers to the local PO creation replicated in R/3.
In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
Regards.
Vadim

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

How is PR created in Extended Classic Scenario

Hai friends
How is PR created in Extended classic Scenario
Please let me know
Regards
Krishna

Hi krishna,
Shopping cart in SRM is equal to PR in R/3.If it is Classic scenario we can customise to create PR in backend for the shopping cart in EBP , but in ECS directly PO will be created against the shopping cart in EBP and it will replicate to R/3 system.
Regards,
Baparao.

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

In an extended classic scenario, how can we make few purchase orders to sta

Hi All,
In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
Thanks
Murali

Murali,
As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
In this the filtering can be done at two levels.
1. Data Filtering
2. Segment Filtering
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Look at BD64 where you can do the config for data filtering.
Regards,
Ravi
Note : Please mark the helpful answers

How differentiate POs classic scenario and POs extended classic scenario?

Hi Gurus,
Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
The objective is determining the following: Is necessary differentiating POs created in SRM of importation and should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
Thanks for your help!!

Hello,
Yes this is possible.
You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
Then you set exceptions in the BAdI.
Regards
Franck

SRM PO Pricing condition from SRM to ECC -Extended Classic Sceanrio

Dear SRM experts,
We have created couple of conditions in SRM7.0 and ECC 6.0 as per requirement. When we create PO in SRM and If we add any condition in SRM PO, PO is getting transferred with netprice(including condition amount).
We would like to see conditions also in ECC which are there in SRM.
For ex:
I have created SRM PO with net price 30 and having freight amount(15) in that PO with Fregiht condition type but when it comes to ECC PO net price is changing from 30 to 45.
We would like to see net price as 30 and 15 as Fregiht condition.
Overall I can say that Is it possible to pass conditions from SRM to ECC in Extended classic scenario.
Thanks
Ravi

Hi,
the challenge lies in synchnizing the conditions and ensuring that price returned by IPC in SRM matches the price in the backend.
Please see thread
Pricing Conditions
Regards
Azad

Activate extended-classic by badi -- PO not created in ECC

Hi,
in certain circumstances I activate the extended-classic escenario in SOCO using Badi BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS:
'logical_system = 'ECCSYSTEM'.
I do this because i need to launch the PO workflow in SRM for the PO created in the SOCO. The problem is the PO is created with the 'saved' status, not in 'order' status, and also when it approves such requests are not replicated to ECC.
If i change the scenario with the BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO Badi I have no problem, the PO is created with 'order' status and when i approved the PO is replicated inmediately in ECC.
Any idea about this problem?
The scenario is classic in srm 7 with ehp8.
Thanks.

Hi,
I would believe the configuration is not properly done in your system.
The BADI BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO is the only BADI you can used to adjust if ECS PO will be created.
By using the BADI BBP_DETERMINE_LOGSYS, it has instead lead to a SRM local PO is requested for and this PO will never replicated to the ERP. If you are not requiring it, please leave this BADI completely.
ECS PO will always be ordered when the PO information is complete. It will be HELD status when the information is incomplete. If you encountered HELD status, it means a purchaser has to complete those missing information first before the ECS PO can be saved. Do you have some customer fields that are mandatory but not populated in the SOCO creation and this lead to HELD status?
Regards.
YS

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

SRM Extended Classic SC Attachments to PO documents in ECC

Hi Experts,
We are attempting to pass attachments using extended classic with the BAPI_DOCUMENT_CREATE2 in the ECS PO out badi. We have been unsuccessful so far. Does anyohne has a solution for this?
Many Thanks,
Paul

Hi Ravindra,
Yes, we are trying to attach to the item level. The same as when you use the classic scenario. Since it is not supported in the extended classic scenario we are trying to do it ourselfs in the po out badi used for extneded classic.
Regards,
-Paul

IR_IND indicator in purchase order - Extended Classic

Hi All,
We have a scenario where we purchase free item from vendors. We reset IR_IND in SRM PO then replicate into backend where IR receipt is reset and Free item is set. We have implemented badi BBP_DOC_CHANGE_BADI and BBP_ESC_PO_OUT to do so but POs always in held status and fail to replicate into backend. Our abaper found the changes in BADI has been overwritten by standard code - system will overwrite it with vendor data. Also we found relevant note 1260486 that stated this is truth - our badi changes will not be kept.
For this case, can anyone help/advice how can we purchase free item in extended classic scenario? thank you.
regards,
glen

Hello,
Not sure if I follow exactly the comments about being overwritten from the partner data, but we do this successfully in an implementation of BADI BBP_ECS_PO_OUT_BADI. In particular in our case we set the GR/IR flags based on a couple of criteria like the document type and amount; I don't recall all the technical details of the structure elements in the subsequent BAPI calls to create or change the PO (BAPI_PO_CREATE1 and BAPI_PO_CHANGE) regarding the free goods flag (UMSON) in the ECC PO, but FYI it is mutually exclusive to try and set the IR flag on a free goods item, the BAPI ignores it if IR is set as I remember.
Hope this helps a little
Cheers
MC

How to close extended classic PO in ECC...

Similar Messages

Maybe you are looking for