SRM7 classic scenario - backend PO creator and item requisitioner

Hi all,
In our current SRM4 with backend ECC 6.0 EhP4, the backend system was defined as ERP_2.0. After shopping cart get approval and PO generated at backend, both the PO creator and item requisitioner are equal to shopping cart creator.
We are upgrading to SRM7 and exploring the service procurement scenario (transfer service hierarchy) between SRM7 and backend ECC 6.0 EhP4. After we defined backend system as ERP_4.0 (LOG_MM_P2PSE_1 activated EhP 4) and setup PI, the PO was successfully created at backend via XML message. However, we noticed that the PO creator and item requisitioner were WF-BATCH but not the shopping cart creator. Is there any setup that can resume both the PO creator and item requisitioner equal to shopping cart creator?
We also tested in SRM7 to define backend system as R/3_4.6C (does not require PI), then the backend PO creator and item requisitioner are equal to shopping cart creator.
Regards,
Donald

Hi Donald
988490
- CHECK CODE CORRECTION
IF NOT ls_partner-requestor IS INITIAL.
      mc_assign_x ls_be_item preq_name ls_partner-requestor.
    ELSE.
      mc_assign_x ls_be_item preq_name sy-uname.
    ENDIF.
Note 761630 - WF-Batch in change documents
Reason and Prerequisites
There are processes in which changes to the document are implemented in the background task in the background (for example, by the workflow). In this case, the system user WF-BATCH is displayed in the document as the last 'Changed by'.
Solution
This is not a general error because the change history correctly displays changes made by the workfow, for example.
In some cases, it would make sense, from a business point of view, that the change history does not display the WF Batch but the user who triggered the workflow/background process (example: approval of a shopping cart by a manager). Due to the complexity of this development, which involves adjustments of all workflows and background processes, no solution can be provided in Releases SRM 4.0 and SRM 5.0. An advance correction is only possible for the special case when shopping carts are released (see Note 761293).
by the way what are your rfc user names?
Check with SAP.
mUTHU

Similar Messages

Classic Scenario -Backend settings

Hi,
In the classic scenario the following is done in SRM
1. In the PPOMA_BBP - we are defining the Attribute : BSA - as EC
2. How this is linking with the Backend in SAP R/3.
We have created the Logical system-in SM59 and RFC are assigned to SRM and SAP R/3.
Backend SAP R/3
1. Number Ranges for P.O defined?
In SAP R/3 -SPRO -Define Document types -We can see the Type EC
How is the linking is achieved in SRM and Backend in classic scenario,.
Can you explain in details what are the setting done in SRM and SAP R/3 to achieve the Classic scenario
Regards
G.Ganesh Kumar

Hi,
Some of the basic settings around document types in SRM for the classic scenario which you have to define are the following :
In R/3 system:
1. define number range for the POs , PREQs and Reservations which will be created in R/3 system,
2. create document types for PO, PREQs and Reservations and assign to them the number of the number ranges created in step 1 - this is the doc type which you have to assign to BSA attribute
In SRM system:
1. define SRM transaction types
2. Define shopping cart number range, as well as the number range of the follow on documents created in R/3 system
3. Define number range for local confirmations of services and goods receipts
Regards,
Desislava

Reference to SC in classic Scenario

Dear SAP gurus,
We're planning to install SRM 7 EHP 2 with backend ECC 6 EHP 5. We plan to use classic scenario, as we know that now, classic scenario already support Sourcing Cockpit and creation of RFx/Auction referring to SC.
However we want to clarify somethings. As I know, the control for classic scenario can be set to 2 things:
a. If stock available create reservation,
b. If external, create PR if no source found.
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend. In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
Appreciate if someone can shed some light of system behaviour in this case.
Best regards,
John

Hi
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Ans: In classic scenario for a non stock item if the source is not there,after the SC is approved it will create PR
in the backend.
In Extended classic sceanario(ECS) if the Sc is not having source once the SC is approved it will go to Sourcing cockpit
(or) you can see in Purchaser worklist
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend.
Ans : In ECS if you creating Rfx to PO in the tracking tab you can see the SC.
In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
This is not clear
G.Ganesh Kumar

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Completion workflow in extended classic scenario

Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
Patrícia

Hi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth

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

Bidding Engine in Classic Scenario

We are implementing SRM7 with Bidding Engine. According to this forum it is possible now to use Direct Procurement (Plan-Driven Procurement) in both Classic and Extended Classic scenario.
However, according to SAP, Bidding Engine can only be used in Extended Classic scenario - is this correct? Can someone please confirm as we are looking to use a Classic Scenario with Direct Procurement and Bidding Engine. Requirement is to have both Project procurement (requisitions from ERP) and shopping cart in SRM, going to Sourcing (RFQ/Bid), and creating the leading PO in ERP, not SRM.

Hello Monica
Bidding is possible both in Classic and Extended classic deployements
As of SRM7.0, you can directcly route the PRs (projects/MRP) from ECC to create a RFx in Bidding Engine. You will need activate the relevant SOA service and a BADI to be activated.
Following information may helps you
++++++++++++++++++++++++++++++++++++++++++++++
Implementing BaDI for RFQ Request SUITE Request
In order to use the SOA RFQRequestSUITERequest message, you have to
implement the BaDI named BBP_EBPXML_OUT_BADI. Please create a BaDI
implementation for the interface: REQUESTFORQUOTE with the following
code:
METHOD if_ex_bbp_ebpxml_out_badi~requestforquote.
use SOA system type to get the SOA interface
from bbp_function_map.
cv_system_type = 'ESASAPXML1'.
ENDMETHOD.
+++++++++++++++++++++++++++++++++++++++++++++++++
Thanks
Kiran

SUS for classic scenario

Hello All,
Is it not possible to set-up a SUS for classic scenario? if so, can some one tell me why?
We have a ECC- EBP classic scenario for direct procurement and plan to leverage the same EBP to set up a SUS . SUS will be on a different client and we would like to use EBP-SUS for indirect procurement.
Please advice. will award points for sensible answers
S

in the case of classic scenario --> following restrictions apply
1) since there is no local document created in SRM , it is not possible to send the purchase order document from SRM to SUS
2) document has to be send from R/3 , and it is possible there to order materials and not services....
3) services is not supported from R/3 to SUS.
hope this helps...

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

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

PO not generated at backend in classic scenario

Hi,
I am working with SRM 5.0 in classic scenario.
1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
PO - From 3005000000 to 3008000000
2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
PO - From 3004000000 to 3009999999
4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
I see the following description in Admin login:
Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:
PO no. 3005000532 is picked from no. range PO defined in SRM.
But, in SC screen, I do not see any follow-on documents.
When I check BBP_PD, I find following data:
BE_OBJECT_TYPE    -> BUS2012         -> Follow on Document Object Type in backend system
BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
(However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
BE_INFO_REC    -> 5300002566
Also, I can see two lines highlighted in Red under Stats:
                       Status                            Description                 Inactive
HEADER          I1015                         Awaiting Approval                X
0000000001      I1111                    Item in Transfer Process           X
My doubt is that ,
a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
Why there is an error in transmission of PO?
Please help.
thanks

plz see Peter instructions in this thread
SC: Error in transmission BAPI 001
regards
Muthu

Item in Transfer - classic scenario!!

Hi experts,
I am in SRM server 5.0 using the classic scenario. In a particular case a Shopping cart has been approved but not transferred to the backend system. There were no alerts in RZ20,ST22 & SM21 when checked at that time.
I have also analyzed and found that there is a table entry in the table BBP_DOCUMENT_TAB for the corresponding Shopping Cart and a PO number has been generated.In the details of that entry I find that the object GUID is 00000.
The checkbox is marked as X while the X flag field is blank.
So, under normal circumstance I understand that if entry exist in this table chk whether PO number exits in REF Object no.Then in SE38 run clean REQREQ up and input the logical system name and SC No. and execute. I had run the same but still the status of the Shopping Cart remains Item in Transfer Process.
I even tried to resubmit the SC by using function module BP_PD_SC_RESUBMIT and in the field OBJECTKEY, I put the backend object ID I got from table BBP_PDBEI (PO ID) which should retry to create the backend doc, and then create an entry in BBP_DOCUMENT_TAB, ready for CLEAN_REQREQ_UP.
But even after that the status remained same.
Now atlast I have got an alert in BBP_PD for the SC which states that the
" Shopping Cart ( value of PO ID ) does not exist "
Can anyone guide me as to why this occured and how can I transfer the PO to the backend system ?
Looking forward for your expert Comments and solution..
Thanks in Advance,
Rajesh Rajendran

Hi Marcin,
Sorry for the delay!!! Thanks for the info but i checked up and found that the number range interval has been maintained in the SRM server when i checked through - transaction SPRO -> SRM -> Cross-Application Basic Settings -> Number Ranges - Define Number Rang. per backend System for Follow-on Docs.
But for the backsystem when i went into transaction SPRO->Cross Application Components - > General Application Functions ->Cross Application Document Numbering -> Maintain Number ranges.. when i executed the same I got an error pop up stating " For the object J_1AOFFDOC no sub-object was defined ".
What does this mean ? This should not be the case else all the Classic PO's would not go to backend ..
Can you clarify ?
Thanks & Regards,
Rajesh Rajendran

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
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.

Classic and extended classic scenario with one EBP

Hello Guys
If I have a one EBP and multiple ERP back ends. For one backend, I need to have classic and other to have extended classic scenario. How this can be fulfilled. Is it possible, if so please provide the configuration setup.
Thanks in advance.

Hello,
In BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
you can try this.
Structure Declaration
DATA: ls_item_data TYPE bbps_extpo_badi.
Moving item data to a structure
MOVE-CORRESPONDING item_data TO ls_item_data.
SELECT SINGLE LOGSYS FROM comm_product
                                 INTO lv_logsys
                                 WHERE PRODUCT_GUID = ls_item_data-PRODUCT .
If lv_logsys = 'XXXCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = space.
ELSE IF lv_logsys = 'YYYCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = ' X'.
ENDIF.
Regards,
Neelima

SRM7 classic scenario - backend PO creator and item requisitioner

Similar Messages

Maybe you are looking for