Classic Scenario - ECC Partner Functions in Backend PO

H All,
I've searched the forums and can't seem to find a definitive answer to my question
1. When I create a PO in ECC for a vvendor with one Ordering Address Partner (OA) or one Invoice Presented By partner (PI) the partners are automatically assigned to the PO.
2. If I create a PO in ECC for the same vendor from a shopping cart in EBP then only the VN partner is assigned to the PO.
Should the OA and PI partners be assigned when the PO is created via a SC from EBP?
We are using SRM 5.0 in the Classic Scenario.
Regards
Chris

Hi
I think, we cannot send PO output to multiple partners (vendors) at one point of time.
You need to use the 'repeated output' check box in the 'output' tab of PO in SRM to send the PO to other partners.
Rgds
Reddy

Similar Messages

Classic scenario-SC not transferred to backend,short dump in ecc

hi Guru's,
Classic scenario, sc not transferred to backend, executed FM bbp_pd_sc_resubmit, short dump occurred in the backend stating call function not found
please help
short dump file attached
regards,
kiran

Hi Kiran,
Could you please send the DUMP for analysis.
Please try to use this -
This is the new report BBP_SC_AUTO_RETRANSFER to change the status from
I1111 Item in Transfer Process
I1112 Error in transfer/ transmission
Thanks,
From RBEI,
Snehal

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

PO attachment transfer to ECC - Extended classic scenario

Hi all,
We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to ECC PO?Is this possible in ECS?If so,what are the steps?

HI Alexander,
The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
attachment transfer logic was only implemented in the Classic Scenario.
One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
BADI does (BBP_CREATE_BE_PO_NEW).
We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
1413792 Attachment deleted after changing purchase order
I hope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

Partner functions OA and IP missing for Vendor in Extended classic PO

As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

Hi
Which SRM Server are you using ?
You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.
Here is the Path from SPRO Transaction ->
Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions
Maintain Similar entries as mentioned below.
Function Function Type Usage Description Abbreviation
00000016 0013 B2B Requester RQ
00000017 0007 B2B Contact Person CP
00000018 0011 B2B Bidder BI
00000019 0012 B2B Vendor VD
00000020 0002 B2B Goods Recipient GR
00000025 0014 B2B Portal Provider PP
00000026 0008 B2B Responsible Employee RE
00000027 0017 B2B Ship-To Address DP
00000028 0003 B2B Invoice Recipient IR
00000029 0015 B2B Invoicing Party IP
00000030 0018 B2B Ship-From Address SP
00000034 0002 B2B Plant PLNT
00000038 0001 B2B Sold-to Party ORDR
00000039 0026 B2B Preferred Vendor PRVD
00000051 0019 B2B Purch. Org. Auth. For Release AREL
00000074 0025 B2B Service Agent SERV
00000075 0031 B2B Location LOCA
00000097 0034 B2B Invoicing Party Employee IPEm
Hope this will definitely help.
More details ->
For 1), see these links below ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Classic Scenario PO has multiple OA Partner Functions for Vendor
For 2), see the pointers ->
There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.
In SRM, there is no standard relation betwwen plant and vendor master data.
You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.
Replication of Ordering Address from R/3 to SRM
Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
Partner function Payee in SRM
Adding Partner Function to R/3 PO from SRM in Classic using BADI
Do let me know.
Regards
- Atul

Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
Our Ultimate Aim is - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default Ext. Classic.
We are exploring new CCTR functionality ....but seems complicated and requiered PI...
1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
2. Which BADi is used while creating Local SRM PO ?
Can anyone suggest/confirm please.
Thanks
NAP

Hello,
In classic scenario, only backend contracts can be used as SOS.
In extended classic, local contracts can be adopted as SOS.
If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
Regards,
Ricardo

RE:Business partner functions in customer Master creation

Do we need to send the Business partner functions while creating record in R3 thru MDM.
For any account group i pass the Idoc is expecting all Business partner functions to be defined for the account group to which am trying to create Customer.(As SH,BP,PY..)
Can anyone please explain me in brief the Business partner function -Problem in my scenerio............................Concept of Business Partner function while creating Customer.

In ECC partner functions are used when you have multiple addresses for the same customer. The partner function links those address records together. You could have multiple unique customer numbers on the KNA1 table, but in the KNVVP table (partner functions) you maintain the linkage between the main table records.
Partner functions are not recommended in MDM. These are generally not considered to be "enterprise level attributes" and therefore shouldn't reside in your customer repository in a central create scenario. Additionally, some of the complexity required to model partner functions can't be modeled in MDM at this time. When 7.1 comes out, there is a new data type called "tuples" which supports deeply nested structures, and therefore you could model a true partner function table inside the sales area table.

Questions about SRM PO in Classic scenario

Hello All
I have a number of questions about the SRM PO in classic scenario.
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit?
We are using SRM 7.0
Regards
Kedar

Hi,
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
Sol: In ECC6.0 if the P.O is changed and release strategy is there in ECC6.0 then it follows the ECC6.0 Approval Route.
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
XI is mandatory
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit.
Once P.O is created in ECC 6.0 for the P.R in Sourcing Cockpit, cancelling/reduction will not have a updation in the sourcing cockpit in SRM.
Eg 100 nos P.R is in SRM sourcing cockpit for which you have createdaa P.O for 40 nos is ECC6.0
for the remaining 60 nos PR ,you can create a P.O in ECC6.0
Regards
Ganesh

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

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

Classic Scenario PO has multiple OA Partner Functions for Vendor

Hi,
I have a 'design' issue. My R/3 Vendor has many OA Partner Functions for the different Branches they have and the PO needs to be Faxed to the OA Partner Function number, but the PO needs to be created against the VN Partner Function.
So, how do i do this in SRM? I was going to have a seperate Catalog link for each OA Partner function, but this is not creating the R/3 PO with VN Partner Function of the 'core' Vendor number.
Does anyone have any advice for this?
regards Adam
Using SRM 5.0 (Server 5.5) SP 8 and R/3 4.6C in Classic Scenario - my catalogs are external vendor.

Hi
Please see these links, which might help ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Regards
- Atul

Partner functions in EBP for extended Classic Scenario

Hello Guru's,
I have a few questions on handling partner functions in SRM 5.0 extended classic PO..
We are planning to use a freight vendor partner as one of the partner functions. The PO raised should go to both the parties from SRM.
Is the output handled in SRM or do we have to use the copied PO on R/3 to send it over to the freight vendor.
Could someone throw in some points.
Thanks
Manoj

Hi
I think, we cannot send PO output to multiple partners (vendors) at one point of time.
You need to use the 'repeated output' check box in the 'output' tab of PO in SRM to send the PO to other partners.
Rgds
Reddy

Z Partner in classic scenario - Is possible to transfer ?

Hi Gurus,
I`m working in classic scenario.
SRM 5.0 / SRM Server 5.5 / R/3 4.7
I need your help about Partner Functions in PO.
I have a Z partner created in R/3 that is mandatory in one type of PO (in header) - the partner type is ZE. I need to replicate this Z partner in SRM.
I tried to create a new type of partner in customizing - Define Partner Functions, with Func. Type - 0012 - Vendor, but the system didn`t allow.
Because this, I used one line with Func. Type - 501 (Customer Partner Type:Org) and include my Z partner in field Abbrev.
Like this:
Function: 00000701
Func. Type: 0501
Usage: B2B
Description: Embarcador
Abbrev.: ZE
After this, I created one new type of Partner Schema and linked this new Schema in one type of Bid Invitation (BUS2200) and one type Purchase Order (BUS2201) - the same type of PO that ZE partner is mandatory in R/3.
In test in ITS, the system shows me the field to include the new partner, but when I try to create PO, the system can`t to transfer this new partner from Bidding SRM to PO R/3 and shows me the error message: the ZE Partner is mandatory in this type of PO (I know that this message is from R/3).
Please, somebody knows if is possible to create new partner and transfer it from SRM to R/3 in classic scenario ?
Thanks very much.
Best regards,
Cris
Edited by: Cristina Alkmin da Costa on Jun 30, 2008 3:53 PM

Hi. Patrner functions are generally different in SRM.
Do you want to be able to select from a list of values in SRM and get the value passed to the backend or do you want a fixed value, or can you look the value up from somewhere?
If you want to fix it or look it up you can simply use the BBP_CREATE_BE_PO_NEW BADI to pass the value.
If you want to select from a list of values, I think the only way is to create a custom field, see note 672960, then you can build a custom search help to find the lookup values you require.
Once you have looked them up, you can pass it to the backend using BBP_CREATE_BE_PO_NEW.
Regards,
Dave.

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

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

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

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

Classic Scenario - ECC Partner Functions in Backend PO

Similar Messages

Maybe you are looking for