Extended classic scenario PO not created

Hi Guys,
Hope someone could give me some hints on this.
This is an isolated case.System works fine for all other shopping cart except for below case.
The shopping cart approved and suppose to create the PO. I could see the PO number generated in BBP_PD for the shopping cart. But the PO not exist in neither in SRM or R3. The status for followon document created is active. There is no any error in transfer reported in BBP_PD for the shopping cart.
I tried to resend the the shopping cart using bbp_pd_sc_transfer but it does not solve the issue.
How could I re-trigger the PO creation and update the PO to R3 again.
Thanks in advance.
Mike.

Try TXN SW01 for the business object BUS2121 and the Shopping Cart number; create a instance and ' execute the method 'Set Released'; this must create a PO if not you need to inform your technical team this error, as it might be a technical error and you can simulate this scenario from SW01.
Please reward point if useful.
Thanks
Kasee Palaniappan

Similar Messages

Extended Classic Scenario does not create backend PO

We have SRM 5.0 SP 11 with ECC 6.0 backend (only one comp code, one plant and couple storage locations in the plant). I am configuring extended classic in there with the Org structure having Local Purchasing Org/ Local Purchasing Groups and the ECC Purchasing Org/ ECC Purchasing Groups.
It appears I am missing something; the system creates a Local PO just fine, however, dont see any signs of the system attempting to create a PO in the ECC system (no runtime errors or logs in either system).
In fact, my shopping cart does not show any value for Location (although the Org has the ECC location assigned to the user).
Any help is highly appreciated. Thx.
Raja

ECC 6.0 is ERP_2.0 and not R/3_4.70.
also check the resp org unit consistency with BBP_BP_OM_INTEGRATE
with the option all object types.
if I am not mistaken there are some FMs to push the copt again
like
BBP_PD_PO_transfer
(pl check the syntax... don't have system)
also check on "bachend prgp responcible" for yr ECS settings
also check the logic if you have implemented
BADI control ECS
BR
Dinesh

Classic Scenario PO not creating, only PR

Hi,
I'm using SRM 5.0, in classic scenario to R/3 4.6C. My Shopping Carts to R/3 are complete, but is not creating a PO. It creates a PR. If i run, ME57, assign and process, PR is already assigned a Fixed vendor, and PO is created without any further data being added. (Vendor, price, etc)
I'm confident my number ranges and Doc Type settings are correct.
In SRM customising, my 'Define Objects in BE Sys, has vaild P.Group, Cat Id, R/3 Source sys, Always external and PO if item data complete'.
When I trace RFC, RSRFCTRC, it is calling BAPI_REQUISITION_CREATE. Not BAPI_PO_CREATE1. Vendor master, set to auto create PO, not using material masters. Mat group and Vendor replicated from R/3 to SRM. Tax is calculated in R/3.
Any help appreciated. Is there a FM in SRM to test why its not creating a PO?
regards Adam

Hi
Couple of reasons might be possible ->
1) Try de-activating all the Custom BADI Implementations using SE19 Transaction (name starting with Y or Z) in SRM System for the time being, and then try out again.
Seems to be some BADI - BBP_TARGET_OBJECTS
BBP_TARGET_OBJTYPE might be over-riding the back-end documents creation.
2) Incase above step, does not help, Try creating a PO or PR directly into R/3 system (using ME21N or ME51N Transactions with the Document typeused in SRM), with the same data that is passed in the RFC call (you traced earlier) then see, what is happening in that case ?
Do let me know.
Regards
- Atul

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

Service procurement using Extended classic scenario

Hi All,
Can Extended classic scenarion supports service procurement.
I mean SC with services and PO with services in SRM without hierarchies
If not any work arounds
Abdul Raheem

Hi Abdul ,
Service procurement using Extended classic scenario is not possible
PO wont able to create in SRM .
Thanks & Regards
Pradeep Kumar Dondeti

GR based IV check box suppressed - Extended Classic Scenario

Hello Folks,
How are you doing today ?
We are working in SRM 5.0 Extended Classic scenario.
When created the Local PO in SRM with GR Based IV Check box active, the
follow-on back-end Purchase order is generated without this flag. In
other terms, system is creating the follow-on ECC PO without GR Based
IV check box active. As a result, we are unable to run the ERS cycle.
Back-end system in above scenario is ECC 6.0. And vendor settings are
maintained with GR based IV flag on in both ECC and SRM.
Kindly advice.
Thank you for your assistance !

Hi Ravi and Yann,
Thank you for your inputs. OSS note-956083 can not be applied in my case due to the hight system version (patch level 550).
I have already raised this issue to SAP, but in the lack of proper infrastrucure SAP can not access the system. (BASIS guys are still struggling with it)
Well...let me give you recap-
We have not activated nor implemented any BAdi so far (Vanila SRM 5.0 EC scenario) PO creation for goods is working fine and as desired. But when it come across with PO with limit item or services, system throws an error as -
"PO 5100000263: Service-based invoice verif. requires GR "NO" or G R-based invoice verif."
Would deeply appreciate if you guys can share insight on this issue.
Thank you for your assistance!

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

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

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Freight is not updated in R/3 in the Extended Classic scenario

Friends,
Freight is not updated in R/3 in the Extended Classic scenario.
Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
We have created a condition for Freight (Value and Percentage)in Create
Payment Conditions using the following menu path:
spro
--> Supplier Relationship Management
--> SRM Server
--> Cross-Application Basic Settings
--> Pricing
--> Process Payment Conditions
When creating a Purchase Order in SRM in the "Item Data" tab, there is
a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
from the drop down menu. Here Freight is available. Add Freight and
the PO record in SRM is updated with the Freight Condition. However,
upon ordering, the Freight condition does not transfer to the PO
recordin R/3.
We've heard this can be achieved by enhancement: only ie by implementing
set of BADIs.. But does anyone know WHICH BADIs we need? Or how we could find out? Thanks.

Hi
<b> You can either of these BADIs to handlwe the scenario.</b>
BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system
BBP_ECS_PO_OUT_BADI ECS: PO Transfer to Logistics Backend
BBP_EXTLOCALPO_BADI Control Extended Classic Scenario
Hope this will help.
Please reward suitable points.
Regards
- Atul

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

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

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

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

Extended classic scenario PO not created

Similar Messages

Maybe you are looking for