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

Similar Messages

Classic Scenario- Service Item custom field transfer from SRM to ECC

Hello Experts,
I was looking for a way to transfer custom fields from SRM to ECC(PR/PO) for service items.I am on SRM 7.01 and ECC 6.0 ehp 5.
The same custom fields are getting transferred for Material item using the BADI BBP_CREATE_BE_RQ_NEW.
But the same badi doesnt work for service item transfer.
I would appreciate it if someone could help me with this.
Regards,
Cruiser

You can use the Function Module SPOOL_RQ_CREATE with the parameters as bellow and debug.
REQNO = SC number
REQUIS_NUMBER = as Purchase Req no ( from backend )
IV_BE_LOGSYS = backend logical system.
System will go through the same path as SC bridging to PR.
HTH,
Chandu
Edited by: Chandrahasan H on Mar 23, 2011 3:36 PM

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

Doubts in creation of PO for service PR in classic scenario

Hi everyone,
I'm working with SRM 5.5 in a classic scenario.
I have the following process:
1. A PR for services is created in ECC (Item Category "D")
2. The PR is transferred to SRM as SC
3. A bid invitation is created in sourcing cockpit
4. A bid is accepted
5. A PO is created.
In the 5th step the PO is created locally in SRM. Is this the standard behavior?? Why is not created in R/3?
Thanks,
Ivá

Hi Ivan,
For scenario details pls refer below links:
http://help.sap.com/saphelp_srm50/helpdata/en/d9/cbd33b8dca2c43e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/frameset.htm
What message do you get when you create a PO from Bid?
Are you able to execute the scenario for materials?
Regards,
Prashant

Services in extended classic scenarios

Friends,
We have implemented services in extended classic scenario. When we create a shopping cart with two service lines and same product category here is what happens:
The SRM PO has two lines items but in the backend the PO is replicated with one Po line item and the two service lines from the shopping cart. This causes a inconsistency with the SRM PO line item number and R/3 PO line item number.
Please advise. Any help is greatly appreciated

Hi Donna,
Is is standard functionnality as the backend PO has item type "D" for service in the first line.
Then for sub item, only limits or services (Id or description) are allowed.
The first line is dedicated to product category.
All sublines belonging to this product category are implemented in the sub item in the service tab.
I have opened an OSS message too but for other services bugs.
Please post SAP answers to update SDN community
Kind regards,
Yann

SERVICE ENTRY SHEET IN CLASSIC SCENARIO

Hi,
Please let me know wheteher we can create service entry sheet in EBP in classic scenario.
Regards,
Manu

Hi Ramesh,
We are in SRM 5.0 using Classic Scenario. We are trying to Create Shopping cart for Services with Multiple Service Line items. What is the best way of creating SCs with multiple service line items. If we use request functionality, is it essential to use Bidding process??
Thank you,
Regars,
Ravi

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

Service Procurement in Extended Classic Scenario

Hi,
We are planning to use SRM 7 EHP 1 with backend ECC 6 EHP 4. We are leaning toward the extended classic scenario. However we are a bit confused reading some documentation that saying Service Procurement classic can only be used in classic scenario.
What does this mean? To put this in more simple, can we have this scenario in extended classic deployment:
PDP:
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
Really appreciate if someone can clarify this point.
Best regards,
Josh

Dear Josh,
For your scenarios below:
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
The shopping cart and PO in local SRM system does not support service hierarchy (Service subline) in the system.
PDP:
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Here also, the system will not create po in the local srm system. The local PO cannot support service hierarchy. The system by default create the purchase order in the backend system directly.
Thanks and regards,
Ranjan

Self service procurement and plan driven procurement in classic scenario

hai friends,
i have configured self service procurement and now i am configuring plan driven procurement in classic scenario.my doubt is suppose a shopping cart is created and placed in a sourcing application of the professional buyer.And assume he accomplished sourcing activity and created purchase order .Now purchase order is created locally or in the backed.i am using classic scenario ,now can u tell where the purchase order is located? if i want to place that particular purchase order in SRM it self what will i do? thanks in advance.

Hi Chandra
before going to select Business scenario (self service, plan driven..etc), you must freeze the technical scenario. Depends upon your technical scenario, your PO will be created .
Where PO is created it is called leading system. It is SAP standard.
If you were selected Classic- Po created in R/3.- R/3 is a leading system .
if you were select ECS- > PO will created in SRM and Copy also will be created in R/3 system. In EBP only you can edit the PO not in r/3. here SRM is a Leading system.
regards
Muthu

SRM Classic Scenario & Invoicing Service Purchase Orders through SUS

Hi everyone,
I hope I am able to provide enough information to ask this question. We are running SRM Classic Scenario in addition to SUS. We would like to be able to have our Vendors login to SUS and Invoice us. However, we are being told that in order to do this we will need to install EHP4. We are currently running ECC 6. Could someone help me understand what it is exactly that we are not able to do this as is? I understand that we are able to configure our current system setup to process Material related Invoices but not Services related invoices.
Thanks for your help.

Hi Jellis,
Your vendors can send invoice from SUS but only for material POs (As you are not running ECC 6 with Ehp 4)
If you want the vendors to send you invoice for service POs also, then you need to go with Ehp 4 as service POs are not supported in SUS using IDOC technology. They need to be in XML format only.
Regards,
Nikhil

Central Confirmation in Self-Service Procurement Classic Scenario

Hi all,
can you confirm that we can not use the Central Goods Confirmation where we are using the Self-Service Procurement Classic Scenario? Just to be sure!
We are working in SRM 7.0 SP4 and ECC 6.0.
Thanks!
Maria

Question answered by myself. Was a mistake.

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

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

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.

Classic scenario service PO replication

Similar Messages

Maybe you are looking for