Central Receiver role in Classic Scenario

Hi All
We have a requirement for a user who can enter goods receipt in SRM on behalf of other users.
We tried to set up the central receiver role provided by SAP , however encountered some issues:
1) In the POWL for the central receiver, only the PO's created locally are visible. So none of the Classic PO's in ECC could
be seen
2) When in the" Create Confirmation" screen, I manually searched for a PO, It allowed me to proceed One screen, however I couldn't enter a confirmation as I got an auth error:
Partner xxxxx not found with partner function type xxxx.
I thought the central receiver was entitled to confirm all PO's without question.
Kindly advise
Thanks
Kedar

Hi Ranjan
The only tab I have is Central confirmation & worklist.
I didn't modify the role , but just using the standard portal & SRM role offered by SAP for Central receiver.
Inside central conf, I have the 2 problems I mentioned.
I cannot find backend PO's & secondly when I try to confirm other person's PO/shopping cart I get the partner function error.
Is central confirmation from SRM , even supported in classic scenario?
Thanks
Kedar

Similar Messages

Central Receiver Role

I'd like to set up a central receiver role/person to do goods receipts when the original SC requisitioner is out sick or on vacation. This person should be able to see all open PO's and select only those he needs to do goods receipts. I know there's a central receiver role but I don't know if there's any further configuration (IMG, PPOMA, BAdI) I need to do to enable this process. Any suggestion would be greatly appreciated.
Also, since the central receiver can see all PO's and only perform selective goods receipts, I'm thinking his GR goes not require approval. Is that true?
Many thanks,
SN

Hi,
The Central receiving Trx can be found for in role SAP_BBP_STAL_RECIPIENT. The Trx is BBPCF03.
The role/intent of this central receiver is to receive goods when the requester is out. If his GR requires the approval of the requester, who is out, how is that going to work? Is there anyway to bypass this requirement?
Sundeep: Yes, you can have no approval. This approval WFL is totally dependent on how the business wants to handle it. If they feel, an approval is not required, you can certainnly bypass it. Also if there is a need for an approval, and the requestor cannot approve (vacation etc), then you need to ask business on how do they want to route the approval in such a circumstance? They will have the answer !!
In case no approval required you can use the no approval WFL WS10400010
Hope this info helps !!
Pls assign points for usefull answers 1
Sundeep

Central Contract Management in case of Classic Scenario

Hi,
At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
Please respond only with reference to Classic scenario.
Thanks,
Abhilash

Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
Kind regards,
Tim

Central Contract in Classic Scenario

Hi Friends,
I have done the central contract scenario in Ex classic where Local contract will be distributed to ECC .
Can we use the central contract concept in Classic Scenario and is there any limitation based on scenario.
As in classic the documents are created in ECC , so for central contract also there will be no local contract ???
Can anyone please help me to understand the same.
Thanks
IS

Hello,
Yes, this concept can be used in classic scenario as well.
You can use them as source of supply, since in classic scenario ECC contracts are considered as soruce of supply. Therefore, replicated contracts will be proposed as SOS for shopping carts.
Regards,
Ricardo

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

Central Contract, MDM Catalog, and classic scenario

Dear SAP experts,
We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
Best regards,
John

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

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.

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

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

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

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

Changing existing classical scenarios in ID to ICo post PI upgrade

Dear Members,
Installed a test PI 7.11 system and restored primary PI DEV system backup on to the test PI system and then the test PI 7.11 system was upgraded to PO 7.4 dual stack system. Done with the post up-gradation activities and the test PO 7.4 system was up and running.
Now, all the ID config objects in the upgraded test PO 7.4 system remained as classical scenarios with sender agreement, receiver determination, interface determination & receiver agreement etc.,
Need a clarification here i.e., how to change the existing classical scenarios to ICo objects in the upgraded PO 7.4 test system..? Do we need to delete the existing sender agreement, receiver determination, interface determination, receiver agreement objects and manually build ICo objects for the respective scenarios (or) do we have any other alternative.
I suppose that the Content Migration Tool doesn't suffice my requirement, as the new PO 7.4 system is not a parallel system built against the existing
PI 7.11 system. I directly performed the upgrade activity on the test system and not on a parallel built system.
In this case, can someone advice how to change the existing classical scenarios to ICo objects i.e., manually (or) do we have any other alternative.
Br,
Saiganesh

Hello Martin,
Finally got it. In the migration tool, configured source system also with the same details as the target system and then the migration of classical to ICO was fine.
Closing the thread.
Br,
Saiganesh.

Tolerance key DQ in extended Classic scenario give Backen error message

Dear all,
I am using SRM 7.0, SP 9
Extended Classic Scenario.
I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
I also set up the ECC tolerances:
- Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
- And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
And even with this set up I still get the error message
u201CBackend Purchase Order quantity exceeded by 1 EAu201D
when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
What Configuration am I missing?
Cheers
Ulrike

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

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

Central Receiver role in Classic Scenario

Similar Messages

Maybe you are looking for