PO output determination in Extended Classic SRM 7

Hi,
Has anyone done PO Output in SRM 7 as per the SAP Note 883693 (ECS: PO output determination in R/3)? Appreciate any feedback.
Thanks,
AB

The same error should appear in ST22. Run the transaction and locate this error entry. Then set an external break point at the statement before the dump and run the scenario in debug mode. You should be able to identify the error from there.

Similar Messages

UNCAUGHT_EXCEPTION while creating Purchase Order in Extended classic SRM 7

Hi Experts,
I am getting the following message while creating Manual or SC/PO in Extended classic Scenario (SRM7.0 with ECC 6.0)
Pl suggest what could be the problems.
Error application is coming up.
20091130
E2001
172331
wicomp03
http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
UNCAUGHT_EXCEPTION
An exception has occurred in the procurement document methods
Form: DETERMINE_MATNR of program SAPLBBP_BD_DRIVER_46A
Form: FILL_BAPI_POITEM of program SAPLBBP_BD_DRIVER_46A
Form: MAP_BBP_DPO_TO_BAPI of program SAPLBBP_BD_DRIVER_46A
Function: BBP_DPO_TO_BAPI_MAP of program SAPLBBP_BD_DRIVER_46A
Method: IF_EX_BBP_DOC_CHECK_ICC~BBP_DOC_CHECK of program /SAPPSSRM/CL_PO_TOLERANCE=====CP
Form: DOC_CHECK_BADI_CALL of program SAPLBBP_PD
Form: PROCDOC_CROSS_CHECKS of program SAPLBBP_PD
Form: PROCDOC_UPDATE of program SAPLBBP_PD
Function: BBP_PROCDOC_UPDATE of program SAPLBBP_PD
Method: /SAPSRM/IF_PDO_BASE~SAVE of program /SAPSRM/CL_PDO_BO_PO==========CP
http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
Regards,
Mohan Raj

The same error should appear in ST22. Run the transaction and locate this error entry. Then set an external break point at the statement before the dump and run the scenario in debug mode. You should be able to identify the error from there.

Map Extended Classic SRM Local PO Text to ERP PO Text

Hi Gurus
I am trying to configure mapping for purchase order texts in the SRM 7.0 system. I am using the folllowing configuration:
"Text Mapping for Inbound and Outbound Texts". I am having an issue with the fact that I can't selelct an "External Logical System" when attempting to map the text fields.
This field "External Logical System" is associated with table BBPC_TEXT_EXT, I can't find anywhere in the system to update this table with the external systems?
Does anyone know how this to setup this configuration???
Regards,
-Paul

First establish the logical systems, text objects, and text types for external text mapping in the table BBPC_TEXT_EXT using transaction SE16.

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

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

Technical Scenario Switch: From Standalone To Extended Classic

Hello,
Currently we are preparing the system to change the technical scenario from standalone to extended classic (SRM 4.0)
While the Customizing steps are clear, it isn´t so clear how the data that already exist in the system will behave after the scenario switch.
Before the scenario switch, the purchasing department is closing all open SRM local purchase orders.
Someone has already done this kind of scenario switch?
What were the problems you encounter?
Regards.

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Do let me know.
Regards
- Atul

Automatic PO output Determination do not get trigger for SRM Classic impl

Hello,
We have implemented SRM 7.0 classic scenarios. We have set up system in such a way that whatever user put in Preferred Supplier at Shopping cart while saving the shopping cart we convert it to Supplier partner type and once approved create PO in ERP system.
Things are working perfectly fine but the problem we are facing is Output determination. We have Vendor email address maintained in vendor master and placed Condition type in MN04 for vendor with Immediate output of email.
But whenever PO is being created that automatic output determination is not being triggered...
Could anyone please help what thing i am missing.
Thanks
Ritesh

Hi,
Please check the created condition record in MN06 in all aspects i.e. partner fucntion name, Medium (5), Language, etc.
I believe you have created the condition record with the combination of vendor/pur.org/document type.
Also check the Actual processing tab and general data is there any check box against Locked field.
Thanks
Rajesh K

Can not generate output via R/3 in extended classic scenarion

Hi,
We are running extended classic scenario, but we want to keep printing, faxing orders via R/3. When an order is replicated from SRM to R/3, the output determination is not working. The messages screen remains empty although the output conditions have been set up. Does anybody have an idea how to resolve this?
Thanks
Ed

Hi
Which SRM and R/3 versions are you using ?
Please go through the following SAP OSS Notes as well ->
Note 883693 - ECS: PO output determination in R/3
Note 886606 - SRM 5.0 SP02: PO hangs in status "In approval": 1 reason
Note 990505 Duplicate entries in transaction SPPFCADM
Note 1028166 BBP_OUTPUT_CHANGE_SF will delete WF when activated
Note 831615 Add page(s) and text to an SRM standard Smart Form
Note 874290 - Problem with output actions
Do let me know.
Regards
- Atul

Extended Classic PO output pass to R3 ?

1. Extended classic Purchase Orders are fully approved (no approval required workflow) in SRM - status "HELD"
2. When we process PO and "order" - the PO is transmitted to R/3 (great, everything seems to be there).
3. There are no messages associated with the SRM (ECPO) purchase order in R3.
Do we need additional configuration to associate a new message type with the SRM ECPO? Should a "message" come along with the extended classic PO as it is transferred to R3?
Hope everyone out there is doing well - !
Best, Jim Stewart
Publisher
www.sapcookbook.com

Hi Jim,
We faced the same problem, but since we are in NetWeaver2004s & ECC 6.0 the new enhancement framework provided by SAP helped us a lot.
Please follow these steps:
1) Maintain the output determination config in R/3
2) In the FM BBP_PO_INBOUND just do a souce code enhancement at the first line. and add the below code which will make R/3 to perform output determination
CLEAR NO_MESSAGING.
This just solved our problem. Since this is an source code enhancement you have no need to modify the std program as well.
Regards
Kathirvel

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

Use of Purchase info records in SRM SC in Extended Classic scenario

Hi All,
We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
Thanks,
Ankur

HI Ankur
when you say the price did not get updated did you check the sequence which is used for price determination ?
1. User entry
2. Contracts
3. Info record
If still you think it is an issue please check the report EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
Regards
Vinita

Extended classic scenario local PO Output status

Hello all ,
Need some inputs on extended classic scenario local PO Output.
My requirement is , when ever the put get process successfully in SRM , I need to send a mail to requester saying that u201C for this particular output got processed successfully u201C
I have business requirement, we need to run this report every 30 min, This report has to pull out the all the PO number from the current time to past 30 min, for the output got processed successfully.
To meet this requirement, I am using the output log entry table PPFTTRIGG where we can see the all the PO with the status and time stamp also.
But some how, this table maintaining incorrect time stamp.
Ex: If I create PO, process the PO output, and if I see the time stamp for this PO, its showing as 10 min before the current time.
Did anybody come across this issue? Or can anybody suggest me any alternative approach for this.
I mean is there any function module/ table available, which will give PO Output status also.
Can you please give me any pointers for this?
Seeking your help on this.
Wish you a advance happy new year.
Thank you.

Hi Latha,
Did you have a look at the standard report RSPPFPROCESS. For PO's please pass the below selection screen values along with the appropiate date & time details:
Application = BBP_PD
Action Profile = BBP_PD_PO
Then regarding the time difference, please make sure that the application server time is sync with the actual time of the time-zone. This could also be a reason.
Then what you can do is to clone the RSPPFPROCESS program and add the email notification logic on that.
Please have a look at the BADI BBP_PROCESS_PO, this can be of some help for your requirement.
Hope this solves your problem.
Regards
Kathirvel

Extended classic scenario - PO print output

Hi all,
Please help me. We have SRM 5.5 (SAPKIBT11) the extended classic scenario.
Could you please tell me Can I print the PO from Web GUI?
If in the Web GUI Output area in PO I set indicator Printer, and to set in Output Pushbutton, in Log I have status - Successfully processed. In trx SP01 the spool status - Compl. But the PO smartforms don't print.
PS: from Output Preview button I can to print the PO smartforms, but I need to print from Output area through the Output Pushbutton. (in the trx BBP_POC or BBP_PPF).
Best regards
Guzal.

Hi, Masa,
Thank you for your advice,
I set the method U:Print Using Berkeley Protocol, after that
in trx. SP01 I have the Error Status on Composite Document -
Status Incorrect (Reason Unknown).
Best regards,
Guzal.

Output from backend in extended classic

Hi Experts,
In extended classic scenario it is possible to sent the output from backend?
Does anyone know have to activate this, and how to deactivate the output control from SRM.
Proces as I want it:
- Creates a shopping cart in SRM.
- Creates a PO in SRM on behalf of the shopping cart, no output.
- The PO from SRM is replicated to R/3.
- The PO is sent to vendor fra R/3.
Best regards
Kim Oster

yes franz is correct. we can do this from consulting note which he mentioned.
PO Output messages for ECS PO's
br
muthu

PO Output in Extended Classic using 3rd party

Hi All,
Would really appreciate if anyone can pls help us out.
We are on SRM 5.0 in extended classic scenario. The client wants to output the PO to some of the vendors in XML but they don't have either XI or BC.
The questions is -
a) Is it possible to send PO to the vendor in SRM in XML without XI or BC.
b)If possible to send PO without XI or BC (The client currently have a 3rd party tool which converts the PO from R/3 to EDI format.).what are the special config required in SRM.
Thanks in advance.
Jay

Hi,
See these related threads:
Re: PO to Vendors
Output Purchase Order from SRM / EBP as File (without XI)
Re: Exporting PO from standalone
Re: SRM 4.0 Send PO to XI
Re: How to define a new "send medium" for a vendor?
Re: PO format (smartform): PDF vs HTML ?
Purchase orders output format.
Re: Data transfer from EBP to external systems
Re: Replicating PO from non-SAP backend to SRM
Re: Data transfer from EBP to external systems
related links:
http://help.sap.com/saphelp_srm50/helpdata/en/84/0783f35c1e11d2b403006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
BR,
Disha.
Pls reward points for useful answers.

PO output determination in Extended Classic SRM 7

Similar Messages

Maybe you are looking for