PO deletion in extended classic.

Hi Experts,
I am facing one problem and I request your valuable solution/suggestion to the below problem.
This is in SRM 4.0 version in Extended classic scenario.
Whenever PO is invoiced and user changes its account assignment in SRM, it goes into error in process.
The problem has been resolved by SAP , but concern is there are some PO which got stuck with Error in process basically its transmission error.
So all these list of workitems are there appearing in the users worklist. where the user does not want these list to appear in his/her worklist.
So anyone can suggest any possible workarround to delete these POs ( which means not the item deletion) the PO number should not appear in the system , or else can there be any solution that these workitem can be forwarded to any dummy user id.
if possible please suggest on my problem.
Appreciate your solution at the earliest.
Thanks in adavance !!!
Regards
SrujanK

Hi
Here first of all once the Invoice has posted, you are not supposed to change the acct assignment data. Suppose if you want to change the account assignment in the PO then you need to cancel all the follow-on documents and then you need to change.
So, Please change the acc to assing to old once and then automatically the PO will come to normal order stage. Then cancel all the follow-on documents i.e like GRN and INvoice, then only the systme will allow you to delete the PO.
BR
Satish

Similar Messages

Extended classic delete purchase order line items

We have a problem with the backend purchase order updating with changes made to the local (SRM) PO. A purchase order was cut with six line items and replicated to R/3 as expected. The line items contained materials. A couple of days later the requestor decided this order was not needed so the buyer went into the local PO and deleted the line items. The local PO looks fine but the backend PO has not been updated. I am recieving an alert message that states the following: "The material 0 does not exist or is not activated. BP_PD_PO_TRANSFER_EXEC". We do not have a material 0.
I've done an OSS search and came across note 918450. It mentions some issues with account assignment indexes for the extended classic scenerio. I've implemented the note and ran the program BBP_EXT_PO_ACC_INDEX, however nothing has changed with the backend PO. Also the note doesn't give much information on what should be done once the code changes are made.
Can anyone give me some insight on how I might find out what the problem is?
Best regards,
Shawn O'Connor

Hi Shawn,
We had a similar problem before - we didn't get the alert message though. We implemented note 601073 in R/3 and the R/3 PO is updating fine now.
Regards,
Paula.

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

PO status Held in extended classic scenario

Hello SRM gurus,
         I am very new to SRM with MM background. I have a question which i think you guys might have come across earlier.
We are using version 5.5 extended classic scenario, replicated all the vendors and materials from R/3 to SRM, did all the basic configuration needed, we are able to see those vendors and materials in SRM also. here is the issue. we are trying to add an item to the shopping cart which in turn creates a PO in SRM so that it automatically replicates in R/3. But the PO status in SRM is Held and we found out that vendor is not assigned to the PO which is very clear why the PO has been held. So what could be reason the vendor is not getting assigned to the PO though we have the inforecord and source list(checked the fix indicator also)for the same material and vendor in R/3 ?
I'm sure many of u would have come across this issue. please help me out.

Hi Satya
      Thanks for your quick response.
1) We are using Workflow without approval process
2) I checked BBP_NUM_SUSPO in SRM server. There is nothing in there. Is this the correct number range for PO? I checked OMH6 in R/3. please tell me how to sync it.
   When we try to post it after editing the PO with vendor number, we are getting Waiting for approval error though we have activated Without workflow approval process. let me know why is it showing that error?
We have another strange issue which is, We have assigned a material say M01 to a pur.group P01,Pur.org POrg1 and vendor V01 and have info record and source list, but we don't see this Pur.grp when we create the shopping cart and it defaults to some other pur.grp say AP01 which we deleted long back. can you tell me where it is picking up the deleted ones?
thanks
Pradheep.

Local SRM PO intead of Extended Classic

Hello,
Does anyone have any idea how best to resolve the following problem.
We are using SRM 5.0. We have managed to create a Local SRM PO instead of the Extended Classic scenario and so the PO will not transfer to R/3 (where the invoices are entered). The confirmation has also been created in SRM.
Please could someone advise on the best way to sort this out (we have fixed what caused the problem so it will not happen again).
Thank you.
Regards,
Jackie

Hi Jackie
Best option is to delete the PO and confirmation and create a new one in SRM as per extended classic scenario.
Sending a local PO to ECC may not be possible in this case.
Regards
Virender Singh

Can not generate output via R/3 in extended classic scenarion

Hi,
We are running extended classic scenario, but we want to keep printing, faxing orders via R/3. When an order is replicated from SRM to R/3, the output determination is not working. The messages screen remains empty although the output conditions have been set up. Does anybody have an idea how to resolve this?
Thanks
Ed

Hi
Which SRM and R/3 versions are you using ?
Please go through the following SAP OSS Notes as well ->
Note 883693 - ECS: PO output determination in R/3
Note 886606 - SRM 5.0 SP02: PO hangs in status "In approval": 1 reason
Note 990505 Duplicate entries in transaction SPPFCADM
Note 1028166 BBP_OUTPUT_CHANGE_SF will delete WF when activated
Note 831615 Add page(s) and text to an SRM standard Smart Form
Note 874290 - Problem with output actions
Do let me know.
Regards
- Atul

Printing of PO in Extended classic scenario

Hello,
Normally the PO print spool gets deleted after 14 days.how do I reprint a PO if reqd after 14 days.PO is not editable in extended classic scenario. so not able to do any change in messages of PO.

Hello,
Any soln for this??
Edited by: JJJ J on May 9, 2009 8:59 AM

Extended Classic Scenerio and Vendor Text

This subject has been brought up before, I've reviewed all those messages. The standard SRM product does not replicate vendor text to the backend system in the extended classic mode.
Having said that, I've been trying to make this work and hope someone here can give me some insight on what I am doing wrong.
In my setup, SRM is using function module B46B_DPO_TRANSFER to send the purchase order to R/3. This fm has a table called i_longtext that contains the header text.
B46B_DPO_TRANSFER calls FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination" to create the PO on R/3. This call is missing the POTEXTHEADER table definition. So, I've modified the call to include this table and also filled the table with the following values:
po_item = 00000
text_id = F01 "this value was obtained from the text type for purchase order header configuration settings in R/3"
text_form = *
text_line = "the message that was typed in the header text"
I can't seem to get the header text to appear on the purchase order in the backend, has anyone been successful in making this work?
Kind regards,
Shawn O'Connor

Hi
Incase BBP_LONGTEXT_BADI does not helps, then you can use the BADI, which i mentioned in my earlier post.
In the BADI - BBP_CATALOG_TRANSFER, there is a table structure, which holds the long text data.
Refer table ET_SC_LONGTEXT inside ENRICH_ITEM_DATA method of this BADI.
Here is the documenatation of this BBP_CATALOG_TRANSFER BADI.
Short Text
Transfer Shopping Cart from Catalog
You can use the Business Add-In BBP_CATALOG_TRANSFER to change or add to the data that the catalog returns to SAP Enterprise Buyer via the catalog interface.
Note that your changes also affect the following applications in SAP Enterprise Buyer:
Confirm Goods Receipt/Service Entry
Plan Products for Maintenance Order
The call of this BAdI occurs in function module 'BBP_WS_IMPORT_SC_DATA'. This module is called by the relevant application to import catalog items previously sent by the browser of the user to the application Web server from there. After the catalog has transferred the data to SAP Enterprise Buyer the system carries out the following actions.
Conversion of ISO code of unit of measure and currency to SAP format
Conversion of price field to SAP format
In the case of transfer of a material or service number:
The system reads the product master with this number. If the number exists, the system transfers from the product master record the description and the purchase order unit of measure.
In the case of a partner number:
The system reads the business partner master with this number. If the number does not exist, the number in the shopping cart item is reset.
Note
In previous Releases, only the tables with the prefix "ENRICHED" were available. These were then returned to the calling application and transferred to the relevant document structure from there. From this Release on, the data is transferred from the current document structure to the application. The relevant tables are included as additional parameters (parameters with the prefix "ET_SC_").
New implementations should use these tables only and set the parameter "ev_sc_structures_used". In order that previous implementations need not be changed, a mapping occurs after the BADI. The parameter controls the mapping direction:
Set: New structure overwrites old structure
Not set: Old structure overwrites new structure
In the method ENRICH_ITEM_DATA, the following parameters are available:
catalog_content
This parameter contains the original data that the catalog transferred to the catalog interface. The structure corresponds exactly to the catalog interface. The data in this parameter is only for information purposes, you make any changes in the parameters et_sc_item_data , et_sc_accounting, et_sc_partner, et_sc_orgdata, et_sc_longtext, and et_sc_messages.
Note
The catalog interface also contains customer fields that you can use for your own purposes. You can pass these on in fields that the application can use further.
enriched_item_data
This parameter contains the data for a shopping cart item in Enterprise Buyer.
Note
This table should not be used in new implementations (see above Note).
enriched_acct_data
This parameter contains all account assignment fields. This parameter is empty at this time in the standard system.
Note
This table should not be used in new implementations (see above Note).
enriched_item_longtext
This parameter contains the long texts for the items.
Note
This table should not be used in new implementations (see above Note).
catalog_content_errors
This parameter contains the error messages that occurred when the catalog items were being enriched.
Note
This table should not be used in new implementations (see above Note).
ev_sc_structures_used
This parameter has to be set if the following tables are used in the implementation (recommended procedure, see Note above) et_sc_item_data This parameter contains the data of a shopping cart item in Enterprise Buyer.
et_sc_accounting
This parameter contains all account assignment fields. In the standard system, this parameter is empty at this time.
et_sc_partner
This parameter contains the links to the requester and the supplier, if used.
et_sc_orgdata
This parameter contains the links to the org. data for the partners from
et_sc_partner.
et_sc_longtext
This parameter contains the long texts for the items.
et_sc_messages
This parameter contains the error messages that occurred during enrichment of catalog items. If this table contains a message of type 'E', the item causing this error is not transferred to et_sc_item_data. If the item is added in the BADI again (from the data from catalog_content), the relevant error message should be deleted, since the current SRM Server application generally searches this table for error messages of type 'E' in order to output an error message to the user.
Hope this will help.
Please reward suitable points.
Regards
- Atul

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

Archive Purchase Order in SRM 5.0@ extended classic senario

Dear SRM Guru,
I use SRM 5.0 in extended classic senario, how can i archive purchase order with limit order using standard SAP?
Thanks.
Regards,
Kim

Hi Kim,
your question is a quite open one. So I try to answer with different flavours - hope there a right one for you.
In case you'd like to archive over system boundaries, i.e. since to ECC PO is a copy of a leading PO in SRM, you might expect that you somehow can archive both at once. This is not happening - i.e. you have to archive both separately.
When you look up notes 726509 SRM archiving: Archiving of R/3 documents with SRM, 723685 SRM: History after the archiving of R/3 documents you might figure out more.
There was an issue in archiving that the workitems were not archived with reference to the SRM document - but this is resolved via note as well. Search for related notes with 'Archiving' + 'SRM' in the service portal.
When you want to figure out more regarding the archiving dependencies you can look up the archiving trx. SARA resp. the archiving programs in SE38: BBP_DP_ARCH_* (CHECK, DELETE, WRITE, SET_STATUS).
Regards,
Richard

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

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

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 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

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 deletion in extended classic.

Similar Messages

Maybe you are looking for