Extended classic scenerio

hi
i am working in extend classic scenerio... i want to create a PO for the backend pur.org and pur.grp ...is it possible to create...
bcz for this type of scenerio we can create PO for local pur.grp and org...i thk so is it correct...
plz give me the detail steps regarding it...

Hi,
In addition to what Suren's reply please find the below points which make you clear about the scenarios :
You can very well create P.Os for back end materials using back end P.Orgs and P.Groups.
Stand Alone Scenario : Only local P.Os can be created using local material / service, local P.Org and Local P.Group.
This P.O will not get replicated to back end. The entire cycle will be completed in SRM. Only the accounting document will be created in the backend Accounting system.
Extended Classic Scenario : P.Os can be created only for back end materials, backend P.Org and back end P.Group.
The P.O is created in SRM and a copy of it is sent to back end R/3 which can be viewed using ME23N txn.
The confirmation and invoice can be created either in SRM system or in R/3 system.
If both stand alone and Extended classic scenarios co-exist then that scenario is called Decoupled Scenario.
Hope this makes you more clear about various implementation scenarios.
Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Similar Messages

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

PO data extraction from ECC to BI in Classic vs extended classic scenerio

HI guyz,
In my project, we are using exteneded classic scenerio for our srm implementation where we fetch shopping cart, purchase order and confirmations data from srm system and invoice data from ecc system BI. also its succesfully running in production system till now.
but a requirement came where for one country we need to use classic scenerio only i.e. we need to fetch po data from ecc system to bi.
please suggest.
regards,
raps.

Hi
please use 2lis_02_hdr, itm and scl for po information and filter the infopackage by country.
Thanks
Krishnan.

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.

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.

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

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 error - extended classic scenario

Hi Guys,
I'm using SRM 5.0 with extended classic scenario...
During creation of the purchase order locally (in SRM) I got the "error in process" status.
My means of T-code RZ20 I got the following info to ithis error:
context:B2B Procurement
object name:Purchase Order
short name: Backend application errors
status: Active
Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
using Transaction BBP_PD I got the following status:
Status: I1080
Description: in transfer to execution system
Do you have any idea what should I do in order to resolve this outstanding issue?
many thanks in advance for your help.
regards,
Piotrek

Hi
Go to transaction - SPAM to get all the required Patch levels and other required system version details.
Meanwhile, try the following SAP OSS Notes as well ->
Note 508972 - Error during transfer of extended purchase orders
Note 881650 - Duplicate transfer/output of the purchase order
PO status in " error In Process ".
Error in Transfer Process (Urgent )
FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)
Hope this will help.
Regards
- Atul

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

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

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

Problem in Extended Classic Scenario related to PO

hi,
we are using Extended classic scenario in our client. User has created a SC .when we are going to create a PO system is showing an error Purchase Group B01 does not exist.
This Purchase group is not created in R3 or neither replicated to SRM.and it is not assigned in the Org structure.
Kindly Let me know from where the purchase Group might be Picked apart from the org Structure.
regards
subhash

Hi
Can you check your SC how this Purchase group picked form your basic data ?
since this purchase group is existing in srm thats why it picked while create sc right?
regards
Muthu

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

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
 You can either of these BADIs to handlwe the scenario.
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 scenerio

Similar Messages

Maybe you are looking for