Replication of PO in Classic Scenario

hi,
in classic scenario, when we create a SC it is creating a PR in backend system.with reference to that PR i am creating a PO in backend system.but the same PO number(copy) has been replicated to EBP system.on what basis it is replicated.
is there any program that needs to be scheduled in backend system?
kindly calrify my doubt.
regards
subhash

dear Muthu,
i have created a SC in EBP where it created PR in backend and w.r.t PR i have created a PO.
now i need to do confirmation of SC in EBP.if i complete my confirmation in EBP material document will be created in backendsystem also.
My doubt is how we are able to do confirmation in EBP for that particular SC w.r.t what?
please calrify this
regards
subhash

Similar Messages

Classic scenario service PO replication

Scenario:-
Classic Scenario
No PI(Process Integration)
No PDP (Plant Driven Procurement) process
Today we created new Service purchase requisition (which is never adopted for PO creation) which contains only one item(10), under this line item (10) five service Numbers…as 20000000(Line-10),20000021(Line-20),20000025(Line-30),20000033(Line-40),20000058(Line-50)
then
Our process:-
Purchase Requisition(Service) Transferred from ECC to SRM - >Purchase Requisition Converted in to shopping cart in SRM> Shopping Cart goes to sourcing -> buyer
creates RFx by adopting the Shopping Cart -> RFx is sent to bidder -> bidder will respond >RFx Response number will be created in SRM>Buyer will compare the RFx responses -> Buyer will click on the RFX response number of L1 vendor>in the RFX response screen when he will click on the “CREATE Purchase Order”
Issue:- why in Service PO items are splitted in to item-10,item-20,item-30,item-40 which is not same like in Service PR
Hope if above issue will solved below error message wont appear
Error Message:-
Materials of requisition 2100000654 item 00010 alr. ordered in full
Message no. 06076
Please Find the attached screen shot
Thanks
Madhu

Can you please elaborate more on this .
from what I understand you want the SC item to not split into different PO generally it spits based on different shipping address maintained . You can also check this in BADI ZBBP_GROUP_LOC_PO
Below is a sample code I found from one of the earlier threads as below :
http://scn.sap.com/message/2772557#2772557
http://scn.sap.com/message/3155145#3155145
http://scn.sap.com/message/2877448#2877448
http://scn.sap.com/message/2371974#2371974
https://scn.sap.com/thread/2026160
https://scn.sap.com/thread/54153
METHOD if_ex_bbp_group_loc_po~group_po. 
*------------------------------------------------------------------------------* 
* Exit Grouping of Items for Local Purchase Orders 
** Parameters 
*ITEM_DATA TYPE BBP_INT_ITEM_GROUP Item Data for Shopping Basket Item 
*It contains the most important item details of the shopping cart and 
*additionally in the field REFNUMBER a reference number for further 
*processing purposes 
*------------------------------------------------------------------------------* 
* Method used to group item before PO creation 
* How it work ? 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
* 2/ Getting Compoents from existing type BBP_INT_ITEM_GROUP 
* 3/ For each line recalcul Refnumber 
********************************************************************** 
* Declarations 
********************************************************************** 
*--------------------------------------------------------------------* 
* Variable 
*--------------------------------------------------------------------* 
DATA: lt_zpo_split_criter TYPE TABLE OF zpo_split_criter 
 , ls_zpo_split_criter TYPE zpo_split_criter 
 , lo_struct TYPE REF TO cl_abap_structdescr 
 , lt_field_list TYPE ddfields 
 , ls_field_list TYPE dfies 
 . 
 
DATA: 
 lt_item_data TYPE bbp_int_item_group 
, ls_item_data TYPE bbp_int_item_groups 
, ls_back_data TYPE bbp_int_item_groups 
, ls_modi_data TYPE bbp_int_item_groups 
, l_fname TYPE fieldname 
, l_refnumber TYPE refnumber 
, l_tabix TYPE sytabix 
, l_not_empty TYPE c 
, l_act_not_empty TYPE c 
. 
*--------------------------------------------------------------------* 
* Field symbols 
*--------------------------------------------------------------------* 
FIELD-SYMBOLS: <lfs_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_act_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_field_value> TYPE ANY 
 , <lfs_act_field_value> TYPE ANY 
 . 
*--------------------------------------------------------------------* 
* Constants 
*--------------------------------------------------------------------* 
* CONSTANTS: 
* . 
********************************************************************** 
* Process 
********************************************************************** 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
SELECT * FROM zpo_split_criter INTO TABLE lt_zpo_split_criter 
 WHERE split EQ 'X'. 
CHECK NOT lt_zpo_split_criter[] IS INITIAL. 
DELETE lt_zpo_split_criter WHERE fieldname = 'REFNUMBER'. 
 
* 2/ Getting Compoents from existing type 
lo_struct ?= cl_abap_typedescr=>describe_by_name( 'bbp_int_item_groups' ). 
CALL METHOD lo_struct->get_ddic_field_list 
 EXPORTING 
 p_langu = sy-langu 
 p_including_substructres = abap_true 
 RECEIVING 
 p_field_list = lt_field_list 
 EXCEPTIONS 
 not_found = 1 
 no_ddic_type = 2 
 OTHERS = 3. 
IF sy-subrc <> 0. 
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO 
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. 
ENDIF. 
 
LOOP AT lt_zpo_split_criter INTO ls_zpo_split_criter. 
* Verify if field exist in table 
 READ TABLE lt_field_list 
 TRANSPORTING NO FIELDS 
 WITH KEY fieldname = ls_zpo_split_criter-fieldname. 
 CHECK sy-subrc EQ 0. 
 
* Copy table in internal 
 lt_item_data[] = item_data[]. 
 
* Sort table by REFNUMBER and fieldname 
 SORT lt_item_data 
 BY refnumber (ls_zpo_split_criter-fieldname) 
 ASCENDING. 
 
* Clear internal value. 
 CLEAR: l_refnumber 
 . 
 
 CONCATENATE 'LS_ITEM_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_ITEM_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_refnumber>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_refnumber>. 
 CHECK sy-subrc = 0. 
 
 CLEAR: <lfs_refnumber> 
 , <lfs_field_value> 
 . 
 
* For each reccord in table, calculate new REFNUMBER 
 LOOP AT lt_item_data INTO ls_item_data. 
 MOVE sy-tabix TO l_tabix. 
 IF <lfs_act_field_value> IS INITIAL. 
 MOVE ' ' TO l_act_not_empty. 
 ENDIF. 
 
 IF ls_zpo_split_criter-as_not_blank IS INITIAL. 
* Case of each value on field create a new refnumber 
 IF <lfs_field_value> NE <lfs_act_field_value> OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE <lfs_act_field_value> TO <lfs_field_value>. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 ELSE. 
 IF l_not_empty NE l_act_not_empty OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE l_act_not_empty TO l_not_empty. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 
 ENDIF. 
 ls_modi_data = ls_item_data. 
 ls_modi_data-refnumber = l_refnumber. 
 
 MODIFY item_data FROM ls_modi_data INDEX l_tabix 
 TRANSPORTING refnumber. 
 ENDLOOP. 
ENDLOOP. 
 
ENDMETHOD.
 
 
 
It works with the table ZPO_SPLIT_CRITER as bellow: 
CLIENT MANDT 
FIELDNAME FIELDNAME 
SPLIT BOOLE_D 
AS_NOT_BLANK BOOLE_D 
 
If you need more information, contact me directly. 
Regards, 
 
David BOUTIER 
Consultant technique Sap Netweaver - KALYDIA 
8, rue Pasquier - 75008 Paris

Extended Classic Scenario-Replication of Local PO to R/3 fails

Hi,
In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
Can anyone suggest if we are missing anything.
Regards
garugu

Hello,
this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
Rgds
Christophe

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

Info Record Not Appearing for all materials in classic scenario.

HI ALL,
 I am working on Classic Scenario and all the follow-on documents are getting created properly. But the problem is With SOS. Currently i am able to view the info record for only one of my material, I am also referring backend contracts through vendor list. The contracts are visible in SOS.
 Can somebody pls put a light as to why for other materials the info records is not displayed in SOS, is there a report which has to be run to get the info record into SRM from ECC. If not then how does the system bring these contracts and info record from ECC to SRM.
 I am working on SRM 5.0 and ECC 5.0.
THANKS AND REGARDS
Debu

Hi
Please read this as well.
You have created sources of supply. These could be:
-> Contract items in Enterprise Buyer
-> Vendor-specific prices
For this, you have created Product Linkages in the SRM System with vendor-specific prices via the SAP Menu Master Data -> Products -> Process Products.
-> Entries in the vendor list of Enterprise Buyer
In Customizing you have assigned product categories to which the system is to automatically group requirements and you have scheduled report BP_SC_TRANSFER_GROUPED to run periodically.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server -> Sourcing -> Define Interactive Sourcing for Product Categories.
Sourcing is completely integrated with the global availability check in SAP APO and executes a vendor search. You can activate third-party order processing in the check instructions by choosing how you want the system to start sourcing and which sourcing method you want to use for it. There are two different options here:
○ If you want the products to be delivered exclusively by external vendors, the system performs sourcing directly at the external vendors without evaluating internal locations. For this, SAP APO requires corresponding purchasing records, delivery plans and contracts that are transferred from SAP ECC.
○ If you only want to have products delivered by external vendors occasionally, that is to say, if you are unable to deliver the product from your own warehouse stock, choose an ATP profile in which both internal and external vendors are evaluated. In this case, the external vendor is treated like an internal location in SAP APO, and is integrated into location determination in the rule-based availability check.
You can also choose the vendor manually. If you have already specified a vendor as the source of supply in SAP CRM, SAP SCM does not carry out any further sourcing. In this case, SAP SCM merely checks the validity of this vendor and confirms the requirement in its full amount if the vendor is valid.
For more information, see SAP Library for SAP SCM at SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Advanced Availability Check Methods -> Third-Party Order Processing in the Global ATP -> Sourcing in Third-Party Order Processing.
Refer these links for more details ->
Assignment of Existing Sources of Supply
http://help.sap.com/saphelp_srm50/helpdata/en/25/40f23a53cd0e04e10000000a11402f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/fa/84944279c0c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/63/36f2323326da4da25d9d0a06f550a0/frameset.htm
Processing Contracts
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f234a9e242a8be10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/4cc5376848616ae10000009b38f889/frameset.htm
See alsoSAP Note 519794 EBP: Replication of Materials exclusively for Purchasing
SAP Note 505030 (Restrictions for the integration of external requirements).
Regards
- Atul

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

Regarding direct material procurement in Classic scenario.

Hello SRM Gurus ,
We are implementing SRM5.0 classic scenario, (SSP with CCM).
As per standard , Shopping cart for a direct material (Requisition for
stock) will create a follow-on document in SRM only (controlled extended
classic scenario).
Client's requirement is that it should create a back-end PR in R/3 system.
Reason being, the client needs to have only one indenting system and one
procurement system.
which BAPI in R/3 for PR/PO has to be used to create PRs or Pos from SRM. Similarly, RFC which FMs have to be used to update status in SRM.
How to bypass the standard replication mechanism.
Please help me..
Thanks and regards,
Mani
mail id : [email protected]

Hi
Why not go for the BADI -> BBP_TARGET_OBJTYPE
Or
Alternatively using SPRO settings, you can change the standard behaviour of the system based on various attrbutes e.g., for a Particular Product, Item category, etc.
Here is the Path ->
IMG -> Supplier Relationship Mnagement -> SRM Server -> Cross-Application Basic settings -> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
Define Objects in Backend System (Purch. Reqs, Reservations,
You perform this step only if you create your Materials Management documents in a backend system.
You specify the documents that are to be created in the backend system for a requirement coverage request.
The following documents can be created:
Purchase requisition
Purchase order
Reservation
You enter a product category (such as office supplies, or hardware) and/or an organizational unit. The organizational unit contains the purchasing group that is responsible for procuring products in this category.
You can enter the product category generically, such as Office*.
Note
The backend system is determined using the product category in the requirement coverage request item. The item also contains the organizatinal unit.
You can use the Business Add-In BBP_TARGET_OBJTYPE if you wish to implement a different logic for creating documents in the backend system.
Example
If purchasing group 01 wants to procure materials from the category Raw Materials, a reservation is to be created every time.
If materials in the category PC are to be procured, a purchase requisition is to be created every time.
Activities
1. Enter the organizational unit and/or the category.
2. Enter a source system.
3. Choose the procurement type.
Reservation if stock is available, otherwise external procurement
The system creates a reservation if the material is subject to inventory management and sufficient stock quantity is available in the warehouse on the requested date.
Always reservation for materials subject to inventory management
The system creates a reservation if the material is subject to inventory management, irrespective of whether stock is available.
Always external procurement
The system does not create a reservation, but always procures the item externally. In this case, you specify the type of external procurement.
The following options are significant if the system cannot create a reservation (for example, if there is no stock available or for a non-stock item) or the system must not create a reservation (choose Always external procurement).
Purchase order if item data complete, otherwise purchase requisition
The system always tries to create a purchase order. If the item data is incomplete (for example, the vendor or price is not known), the system creates a purchase requisition from the item.
Always purchase requisition
The system always creates a purchase requisition.
Always local purchase order
The system always creates a local purchase order.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Classic scenario CUF to R3

I've been reading about Extended Classic Scenario (ECS) and how to get customer fields (CUF) to R3 using a BADI. Is something possible for the classic scenario also?
I've defined CUF in INCL_EEW_PD_ITEM_CSF* and they show up, but I want to map the CUF to R3 fields.
Maybe it's just a matter of defining the ZFields in the appropriate append-structure??
Regards, Léon Hoeneveld

Hi
Please go through the pointers/links for all detailed sample code and issues you are currently facing ->
Re: Missing Fields
Re: EBP PO Created by WF-BATCH
Re: ECC Purchase Requisition Replication to SRM SC
Re: Mapping fields in SRM with R/3
Re: ACCOUNT ASSIGNMENT
Re: Tax calculation
Re: Add customer fields in Shopping cart and purchase order
Re: Need info on how to set GR-IV indicator
Re: PO created with status : Transfer Failed (E.Sys.)
Re: Bapi BAPI_POEC_CREATE I_PO_LIMIT problem
Re: Error in transmission with BBPSC01
Re: Pass PO Customer Field to Backend System
Re: Problem with BAPI_PO_CREATE1
PO header CUF to ECC
Re: Last delivery option in SRM
Hope this will definitely help.
Do let me know.
Regards
- Atul

Storage locations - Classic scenario

Hi Gurus,
We have SRM 5.0 - Classic scenario
We have a request from business to add attribute Storage Location (LAG) for using in Shopping cart. While I understand that we can maintain this under extended attributes in PPOMA_BBP, the issue to begin with is -
1. How do we get the Storage location attributes populated en masse for all the Plants? It is not possible to maintain them manually. Is there any replication prog?
+2. Even if I maintain the Storage location manually, it still does not show in the shopping cart. will this issue be resolved thru FM BBP_ATTR_TEXT_REFRESH (I'm not sure if its a FM or T code)
Thanks in advance
regds,
SB

How do you order a cart via describe requirement? or good and services?
you must get stoarge location if you order froma good and services in the basic data.
1.It is possible to enter manually. just type your storage location . Automatically Plant will be filled with storage
location.
Are you geting any error here.
2.Are succeed to bring to populate Storage location in Ext.Attribute . if it so
you may need to run the report for staorage location if you dont get for LAG attribute.
Note 1094742 - BBP_ATTR_TEXT_REFRESH Not update the LAG attr. in
background -
Did you see this note
Note 767058 - Company code/plant/storage location are not transferred
The texts are saved in table BBP_ATTR_VALUE_T. You can use report BBP_ATTR_TEXT_REFRESH to update this table with the
descriptions from the back-end system.
LAG is an attribute for storage location
Note 1175255 - RFC_READ_TABLE creates
ASSIGN_BASE_WRONG_ALIGNMENT termnatn
regards
muthu

Creation of Inbound delivery mandatory for ASN process in classic scenario?

Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil

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.

Backened documents are not getting updated in Classic Scenario

Hi,
We are using SRM 7.0 version and we are working on classic scenario where the shopping cart - RFX - Contract are created in SRM and the PO - GR - IR are created in ECC. The blackened documents which are created in ECC PO - GR and IR these documents are not getting updated in SRM system.
Is there any business functions to be activated.

Hi Sunil,
You manually run report ""BBP_GET_STATUS_2" after PO is created in MM. Then check if the follow-on-docs are updated in SC.
If it is working fine after you manully run report, you will have to properly set time to run this report automatically.
Best Regards,
Anu
Edited by: Anuradha UG on May 18, 2010 8:09 PM

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

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

Replication of PO in Classic Scenario

Similar Messages

Maybe you are looking for