No GR on Confirmation Approval in Extended Classic Scenario

Hi all gurus out there,
We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
Cheers!
Siow Fong

Hi Guys,
I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
Regards
Siow Fong

Similar Messages

Question on Purchasing documents in extended classic scenario

Hi friends
How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
Please let me know the path
regards
venkat reddy

Hi Venkat,
The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
Regards,
Prashant
Do reward points for helpful answers

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

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

PO created but Status showing as Awaiting for approval in extended classic

Hi Experts,
SRM 5.0 extended classic scenario,SC approved and PO created but status showing in follow on documents node in SC as awiting for approval.
Can any help in finding solution.Thanks in advance.
Thanks,
Babu

Hi Babu,
I am facing the same issue in the ECS SRM 5.0 after approving the shopping cart the PO created in EBP but the WF status is waiting and PO is not transmitted to R/3. Below is the status of SC and PO in BB_PD. Kindly suggest what could be the problem where i can analyze.
SC
                    Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1106          Shopping cart ordered
HEADER     I1129          Approved
0000000001 I1111          Item in Transfer Process       X
0000000001 I1113          Follow-on Document Created
0000000002 I1111          Item in Transfer Process       X
0000000002 I1113          Follow-on Document Created
PO
Stats:
           Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1180          Document Completed
Thanks,
Kannan B

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
Please go through the SAP OSS Notes below ->
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
Do let me know.
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

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

Payment term key with limit days in Extended Classic Scenario

Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
 ZTERM ZTAGG
 K180 09
 K180 19
 K180 31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
 ZTERM ZTAGG
 E000 00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regards

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 scenario local PO

Hi All ,
Need some inputs on the extended classic scenario local PO.
There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
We can change the same PO from the process purchase order also.
But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
If sy-uname = WF_BATCH
Do the mapping part
Endif,
But I donu2019t think so; this logic will work all the times.
Please can anyone give me some pointer for the same, it will be really helpful for me .
Seeking your help on this
Thank you,

Hi Latha,
This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
Hope you can build your logic based on this; this is a better logic on par with the existing one.
Regards
Kathirvel

Extended Classic Scenario - Can Purchase Requsition be created in R/3?

Hi SRM Gurus,
In Extended Classic Scenario, Is it possible to have Purchase Req to be created in the backend?
Technically whether it is possible or not? Functionally, there is no such need, I agree.
Thanks & Regards,
Ramkumar

Hi
Please confirm what sceanrio in SRM are you planning for ?
I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE" -> I guess, it's possible, but not sure. Try it out.
Purchase Order (PO) will be created in the R/3 system using the BADI - BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
Regards
- Atul

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.

Pricing conditions in extended classic scenario

Hello friends,
I have a question about pricing conditions. There is a condition in R/3 where the price can be redetermined based on the G/R date. Is it to do something similiar in SRM. I mean redetermine the price at the time of confirmation.
Thanks any help will be appreciated.

Hello Chakradhar,
IPC is required for extended classic scenario. Reach out to your basis practitioner, he should be able to perform this.
Helpful links
Re: IPC Configuration in Functional perspective.
Re: IPC Configuration
Hope this helps.
Thanks
Ashutosh

PO Change in Extended Classic Scenario

Hi SRM Experts,
Our client is using ECC 5 and SRM 3 (BBPCRM 4.0) and using classing scenario successfully.
Now we have started using extended classic scenario for limited suppliers.
Now the client requirement is to change the PO after approval.As you know that in ECC the PO can be displayed only.
And the PO already directly submitted to the supplier.
Is it possible to change the PO after submitting to supplier ?
They are looking for some changes in text/shipping address etc.
Appreciate all your suggestions.
Thanks and Regards,
Pradeep

Thanks Masa for your quick reply.
Could you please tell me that,we are using work flow for SC approval and when the Shopping Cart created the WF also starts and finally the SC get final approval the PO will push to supplier directly and the same will be replicated in ECC (display only).
So after activating the version control will it still allow the user to change the SC/PO after completing the approval ?
If so do we need to make any changes in our WF ?
Thanks and Regards,
Pradeep

ASN in Extended Classic Scenario with SUS

Hi SRMer?
Is it possible to create an ASN in SUS with Extended Classic Scenario (ECS)?
OSS note 543544 mention that the scenario is limited for document types Purchase Order, Purchase Order Response and Change Order. Confirmations and invoices are not possible. There is no indication on ASNs.
Any help will be appreciated.
Regards.

Hi
Please go through these links ->
SUS-MM Confirmation without ASN
Re: Details on ASN
The specified item was not found.
SUS ASN - mandatory field
ASN Confirmation not created,
Clarifications on EBP-SUS and MM-SUS Scenario
Re: SUS-MM scenario with "POR (order ack.)" and ASN for free text
Creating custom field in ASN screen of SRM SUS
SUS Invoice
Regards
- Atul

No GR on Confirmation Approval in Extended Classic Scenario

Similar Messages

Maybe you are looking for