About the Classic scenario,ERP PO number didn't return go Shopping card

About the Classic scenario,We create a shopping card,And approved,the follow document purchaser order create the ERP system,But the Purchaser order number didn't return to the shopping card follow document tab page.How can help me?

Dear Masa ,
Yeah,we schedule program BBP_GET_STATUS_2 and CLEAN_REQREQ_UP,Then have this issue,We didn't know why.

Similar Messages

Number of document created in th backend in the classic scenario?

Dear Experts,
Could you please tell me the number of document and its details created in the ECC backend in the below cases?
1. Case 1:
Define backend objects:Purchase requistion created if no stock available.
Is it correct that the system will create two documents here? The first document will be Purchase Requisition
( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
2. Case 2:
Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
Is it not a violation of standard classic scenario if only one document is created?
Thanks and regards,
Ranjan

Hi,
In other words in the shopping cart is approved
1) If the source is assigned -It will create a P.O in the backend (Classic)
2) If the source is NOT assigned -It will create a P.R in the backend (Classic) .. you have to assign a source
Regards
G.Ganesh Kumar

Confirmations in the Classic Scenario

We are currently running SRM 4.0 and using the classic scenario to create reqs and POs in the backend system. We want to do GR in SRM and have setup the central receiver role. Is there an ALE process that needs to be activated to see the list of POs in SRM?

Hello Nancy,
Check whether you have done below config or not:
1. Creation of Partner Profile using tran WE20 for Message type ACC_GOODS_MOVEMENT & MBGMCR
2. Set up Ports under Transactional RFC using Transaction WE21.
You can also go through this SDN link:
Re: SC not to be seen in check status after MIGO in R/3
Regards,
Shiv

Questions about Extended classic scenario

Hi gurus,
I'm working in SRM 5.0, ECS, backend ECC 6.0 (only one backend).
Everytime a SC is being approved a SRM PO has be created. Then a copy of this PO has to be created in ECC with document Type ATT and the same number of the SRM PO.
I have two questions
First of all I need to know the settings to make in 'Define objects in backend system' (for every purchasing Group and every Category ID, I need to create always PO in backend).
P.Gr Category ID Source System Internal proc. External proc.
* TRDCLNT011 Always external procurement PO if item data complete, otherwise P.Req.
Is this correct?
Secondly I need to understand the logic for number range definition
SRM Activities
1 - Define number range for Shopping Cart
I Need to create a SC number range
01 1000000000 - 1999999999
and then associate this range (01) to SHC transaction type ('Int.n' field)
2 - Define a number range for local PO
LO 7000000000 - 7999999999
and then associate this range (LO) to ECPO transaction type ('Int.n' field)
3- Create a new transaction type 'ATT' (backend PO)
4 - Define a number range for backend PO
PO 7000000000 - 7999999999
and then associate this range (PO) to ATT transaction type ('Int.n' field)
ECC Activities
1 - Define a number range for document type ATT
XX 7000000000 - 7999999999
and then associate this range (XX) to ATT Document type 'External
Is this correct?
I'd really appreciate your help
Points will be rewarded
Thaks in advance
Best regards
Gg

Hi. It all sounds about right.
I don't think the define backend docs does a great deal in ECS, you always get a PO with extended classic. If you ever want anything but a PO, a reservation for example, you have to not use extended classic for those items.
The number ranges look OK, although I think you only need 1 number range for the backend/local POs, it should all go in line on its own. It's been a while since I got an ECS system going so it is hard to remember.
The thing to do is try it in a test system and see what happens.
If anything goes wrong let us know on SDN what error messages you get and we should be able to help.
Regards,
Dave.

Classic scenario using SRM SOCO

Dear Experts,
We use SRM7.0.
We want to use classic scenario u2013 creating backend PO and not SRM PO.
Can we use the SRM SOCO if we want to create backend PO ?
To clarify myself, can we implement this procurement process:
1. SRM SC
2. The SC will go to the SRM SOCO u2013 Sourcing cockpit
3. The purchaser will create backend PO from the SC items on the SOCO
Or in case we want backend PO, we must use ME57 on ECC system ?
Thanks and regards,
Lori

Hi Lori
It is possible to create a Purchase order in the backend from the SRM cockpit ( but it should not be order as Direct) by the Purchaser in the classic scenario.
Are you finding any difficulties ?
shopping cart create and ITS venture to cockpit upon sourcing configuration
add vendor and price in the shopping cart item or propose source of supply
and click PO creation and PO number will be generated from SRM system and PO will be avaiulable in ECC system .
BBP_CREATE_BE_PO_NEW - Purchase Order in Backend System
Using BusinessAdd-In BBP_CREATE_BE_PO_NEW you can change all the data thatis transferred to the backend system for generation of a purchase order. This includes, for example, the item data, the account assignment data, and texts.
All the shopping cart data is available as input parameters.
Ricardo / Lisa - please confirm the same when you read this thread and appreciate your comments here

Automatically create a PO from a catalog buy in the classic SRM scenario

All,
We are on SRM SAPK-70207INSRMSRV classic scenario and R3 EHP6 FOR SAP ERP 6.0
When a shopping cart is created and approved from the MDM catalogue we get an automatic purchase requisition. currently the purchasers manually create the purchase order from that purchase requisition but we want to have an automatic purchase order for every all catalogue buy.
is this possible in the classic scenario ?
Can we also assign specific purchasers to these automatically created purchase orders, based on, for instance, the purchasing group as we use vendor invoice management so these purchasers will receive invoices with a price differences.
Thanks as ever.
Antoinette

Hello Antoinette,
A. Stork wrote:
is this possible in the classic scenario ?
Please have a look at below wiki:
Determination of the follow-on document type
A. Stork wrote:
Can we also assign specific purchasers to these automatically created purchase orders, based on, for instance, the purchasing group as we use vendor invoice management so these purchasers will receive invoices with a price differences.
Depending on product responsability and organizational responsability, purchasing group is automatically determined for each SC item.
For those purchasing groups, users are assigned inside the PPOSA_BBP transaction.
So, i do not understand your request.
Regards.
Laurent.

Some questions about classic scenario

Hi all:
      For classic scenario,I found the SC with indirect material procurement could created a corresponding Reservation or PR in R/3,But for direct material procurement, the SC could not have any courresponding document created in R/3. Does it right.

Hi,
This scenario relies strongly on the Enterprise Resource Planning (ERP) backend system(s), since all materials management documents, such as purchase orders, goods receipts, service entry sheets, and invoices are located there. Enterprise Buyer and one or more backend systems (SAP or Non-SAP) are implemented. All materials management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entry sheets and invoices) exist in the backend system.
SAP Enterprise Buyer is used to create the shopping cart and obtain approval if required. The goods receipt and invoice can also be entered here. SAP Enterprise Buyer communicates this information to the backend system where the active documents are created.
This scenario suits customers:
     Who want a wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP Enterprise Buyers functionality and ease of navigation allow this, as it requires only minimal training
     Who want their purchasing department to operate solely with the functionality offered by the backend system(s)
     For whom a transfer of purchasing activities to SAP Enterprise Buyer is not viable
If collective invoicing needs to be conducted, the classic scenario must be used.
Hope this helps u....
Reward points if useful...
Regards,
Sreenivas

MM-SUS for the extended classic scenario

Hi,
I have done SUS-MM for the classic scenario.
Did anyone implement SUS-MM for the extended classic scenario ?
Did you face any problem or will it be same as 'classic' scenario ?
Please help
Thanks
Pranav

There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
Regards, IA

PO creation problem with classic scenario

Hi All,
We are in SRM 7.0 nad have mapped extended classic scenario. Now we want to map the Classic scenario only for a specific company code. So, my question is can we map the classic scenario on company code specific.
I tried maintianing the document type & number ranges in R/3. Maintained the number ranges & transaction type in SRM.
Also implemented BADI BBP_EXTLOCALPO_BADI.
But after creating the SC the status is "Approved" but no PO getting created in ECC. On observing RZ20 there is an system error for the number ranges.
Please let me know if I am missing some steps.
Thanks in advance.
Regards,
Abey.

HI,
Make sure the PO number range in ERP is same in SRM. Also have the external checkbox checked for PO number range in ERP.
Also have the same transaction type in SRM and ERP. Where the ERP transaction type should have external number range as the above mentioned profile.
Regards
Sam

Extended Classic Scenario

Referring to note 963000, we are about to install SRM 5.0 as AddOn to
Ecc ERP 2005. In SRM we would like to implement the "Exteded Classic
Scenario", meaning the procurement process will take place locally in
EBP and a copy of data is replicated to the beckend system (ECC).
Is the "Exteded Classic Scenario" compatible with the "SRM as add-on"
installation? Note 963000 sais "The following scenarios are released
within SRM AddOn: ... Self service procurement (classic deplyment)":
does that mean that only the "Classic scenario" (meaning only Shopping
cart on EBP, the rest of the purchasing process on backend) is
available?

HEllo,
Only self-service scenario is supported. Means classic, extended classic and standalone.
HTH
Gordan
Message was edited by: Gordan Flego
Message was edited by: Gordan Flego

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

Extended Classic Scenario - Free Items?

Does SAP support PO's in Extended Classic Scenario with a zero price (free items)?
My client is switching from classic to extended classic scenario and they require to be able to creaet PO's that have a zero price like they have in the classic scenario.
We are currently getting an error that we need a price with the IR flag, but I would expect the system to automatically unflag the IR flag for a free item?

Hi Jay,
Thanks for your response. There are two problems with your soluiton. First the shopping cart doesn't have the IR flag on it and can't be changed by the user and we have PO's created directly from SC's and go out to the vendor.
Second, In extended classic scenario it apprears that the system doesn't allow you to change the ir flag on the PO and make the cooresponding change in the ERP PO.

Item in Transfer - classic scenario!!

Hi experts,
I am in SRM server 5.0 using the classic scenario. In a particular case a Shopping cart has been approved but not transferred to the backend system. There were no alerts in RZ20,ST22 & SM21 when checked at that time.
I have also analyzed and found that there is a table entry in the table BBP_DOCUMENT_TAB for the corresponding Shopping Cart and a PO number has been generated.In the details of that entry I find that the object GUID is 00000.
The checkbox is marked as X while the X flag field is blank.
So, under normal circumstance I understand that if entry exist in this table chk whether PO number exits in REF Object no.Then in SE38 run clean REQREQ up and input the logical system name and SC No. and execute. I had run the same but still the status of the Shopping Cart remains Item in Transfer Process.
I even tried to resubmit the SC by using function module BP_PD_SC_RESUBMIT and in the field OBJECTKEY, I put the backend object ID I got from table BBP_PDBEI (PO ID) which should retry to create the backend doc, and then create an entry in BBP_DOCUMENT_TAB, ready for CLEAN_REQREQ_UP.
But even after that the status remained same.
Now atlast I have got an alert in BBP_PD for the SC which states that the
" Shopping Cart ( value of PO ID ) does not exist "
Can anyone guide me as to why this occured and how can I transfer the PO to the backend system ?
Looking forward for your expert Comments and solution..
Thanks in Advance,
Rajesh Rajendran

Hi Marcin,
Sorry for the delay!!! Thanks for the info but i checked up and found that the number range interval has been maintained in the SRM server when i checked through - transaction SPRO -> SRM -> Cross-Application Basic Settings -> Number Ranges - Define Number Rang. per backend System for Follow-on Docs.
But for the backsystem when i went into transaction SPRO->Cross Application Components - > General Application Functions ->Cross Application Document Numbering -> Maintain Number ranges.. when i executed the same I got an error pop up stating " For the object J_1AOFFDOC no sub-object was defined ".
What does this mean ? This should not be the case else all the Classic PO's would not go to backend ..
Can you clarify ?
Thanks & Regards,
Rajesh Rajendran

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

STO classic scenario SRM 4.0

Hi All,
We create SC that transferred to STO (Stock Transfer Order).
With the Classic Scenario(SRM 4.0) we use BBP_CREAT_PO_BACK.
A STO is created but the number of the STO is not displayed in SC.
Any suggestion ?
Thanks in Advance..
Moti

Hi Christophe
I) In CS - Did you use the scenario were a SC is transferred to a STO in R/3?
II) In ECS - Did you use the scenario were a SC is transferred to a PO in SRM and a STO in R/3?
Here are more detail of whate i have done:
A. In the Classic Scenario
I) Standard Purchse Order (this one works fine):-
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document from EC to NB,
2. Changing the Vendor from 1000000272 to 1000000271,
Run the program - CLEAN_REQREQ_UP.
The system as expected - A PO is created and
In the Follow-on Document, in the SC, I get tow messages:
1. Shopping Cart 1000000508/1 Follow-on Document Created
2. Purchase Order 4400002238/1
II) Stock transport Order (here the problem arises):-
In order to create a STO
I adapted the BADI BBP_CREATE_PO_BACK as follows :
1. Changing the document type from EC to UB (STO),
2. Changing the Vendor to a Supplying Plant 236 (The central warehouse),
3. Changing the Item category 7 (U - Transport),
Run the program - CLEAN_REQREQ_UP.
A STO is created (Number 4400002239) but the number of the PO is not in
the SC.
In the Follow-on Document in the SC I get only onr tow message:
1. Shopping Cart 1000000511/1 Follow-on Document Created
To confirm the goods receipt of that STO from the status screen I get the messsge: 'PO 1 contains no items for confirmation'.
When confirming the goods receipt from the Confirm Goods/Service I get the message: 'PO 4400002239 contains no items for confirmation'.
B. In the Extended Classic Scenario
I adapted the BADI BBP_ECS_PO_OUT_BADI as follows :
Document type - UB (STO),
Supplying Plant 1000 (The central warehouse),
Item category 7 (U - Transport),
The BADI use the BAPI BAPI_PO_CREATE1.
The BAPI_PO_CREATE1 returns the following listed error messages:
'Net price must be greater than 0'.
Because the BAPI is activated whith extra parameters like: Invoice Receipt Indicator and Partial Invoice
Your help is appreciated.
Rgds
Yoram

About the Classic scenario,ERP PO number didn't return go Shopping card

Similar Messages

Maybe you are looking for