Purchase Order Printout

[Former Member]

Hi all,

We are on SRM 7.0 and ECC 600. We are running Extended Classic Scenario.

PR-SC-BID-SRM Leading PO - ECC PO

The transferred purchase order in ECC is not determining the message class NEU in Messages.

IIn the extended classic the printout is mandatory to be done in SRM or could be done in ECC also?

Thanks

Ezequiel

[Former Member · Accepted solution]

HI

As you aware , in ECS, PO Messages will be created in SRM not in ECC PO.

but SAP offered a consulting note to create a PO MESSAGE in ECC as well.

br

Muthu

[Former Member · Accepted solution]

Hi Muthu,

Is this note you are referring? Note 1242555 - PO output data not determined in backend

After implementation of this note message NEU will be determined and then it will be possible to print it from ME9F?

Note 1242555 - PO output data not determined in backend

Symptom

Extended classic scenario.

You have created a purchase order and transferred it to your SAP backend system.

You then change the purchase order and transfer the changes. You find that the changed backend purchase order is not as expected because within the backend purchase order processing the "xneudruck" value (program SAPMM06E) is not determined.

Other terms

BBP_POC, xnast, ynast, print, output, schedule, EKET, SLFDT, delivery date

Reason and Prerequisites

Prgram error

Solution

Please implement this note.

[Former Member · Accepted solution]

Extended Classic Scenario (ECS):Purchase Order output determination in R/3.

.

This note is a consulting note. And customer can implement the note himself as a modification. And this behaviour is not in SRM standard.

The first step described below is valid only for SRM 4.0 (SRM_SERVER 500). And will not be included in support packages. And it has to be implemented manually. This note is valid only for PO's created using Extended Classic Scenario.

General behavoiur of Extended Classic scenario in SRM

When using Extended Classic Scenario, SRM takes on the role as the

purchasing system so that the EBP PO (local PO) is the 'controlling' PO. The local PO is copied to the backend but only to the extent that

this is necessary for the follow-on steps (confirmation and invoice).

No changes can be made to the PO in the backend. R/3 output determination does not work in the extended classic

scenario. The PO must be output using EBP.

The PO output of the backend PO is deactivated. The reason is that we offer output functionality in SRM and do not want to offer this functionality twice.

With this consulting note customer can able to activate again the PO

output determination at R/3.

Steps to activate the PO output determination in R/3 in case of ECS.

And vaild for SRM 4.0 (SRM_SERVER 500) , SRM 5.0 (SRM_SERVER 550) and SRM 6.0.

====================================================================

For SRM 4.0: To prevent the output determination in SRM for extended classic scenario firstly deactivate the class CL_ACTION_PO_OUTPUT_BBP.

For SRM 5.0 & SRM 6.0: To prevent the output determination in SRM for extended classic scenario firstly deactivate the class CL_BBP_ACTION_OUTPUT_PO.

How to achieve this, Goto transaction SE16 and enter the table

name BBPC_ACTIONMAP (this is a cusotmising table) -> click F8.

This displays all the entries for different business objects.

For example: for business object BUS2201 (PO) the entry like this for SRM 4.0:

CLIENT BUSOBJECT ACTION CLASS ACTIVE

300 BUS2201 CL_ACTION_PO_OUTPUT_BBP X

Same thing you can perform for SRM 5.0 but for these two releases deactivate the class CL_BBP_ACTION_OUTPUT_PO.

Goto change mode by clicking the(pencil)icon from the tool bar, and double click on this entry and Remove the flag from the field Active.

Save the table. By doing this, the output determination in SRM is deactivated.

Customising R/3 Output Control:

In R/3 Customise the Ouput control settings . The IMG path for customising Output Control is, Transaction SPRO -> SAP Reference IMG -> Materials Management -> Purchasing -> Purchase order -> Messages -> Output Control -> Tips for Fast message Determination Setup. please go through the Tips for Fast message Determination Setup documention. For additional information about the FAQ's on Message processing in R/3 purchasing, please refer the note 457497.

Defining the Doc type in R/3 for output at transaction MN05:

Path in R/3 for MN05 is SAP Easy Access -> SAP Menu -> Logistics -> Materials Management -> Purchasing -> Master Data -> Messages -> Purchase Order -> MN05 (Change). Here enter the Document type for the PO (Please notice that this Document type should be the same Document type that is defined in SRM and with which the ECS PO is created).

In addition, you also have to do the following change at the include for BAPI_PO_CHANGE.

Include: LBBP_BAPI_POF01

<<<<<<<Context Block>>>>>>>

....

ELSE.

CALL FUNCTION 'FUNCTION_EXISTS'

EXPORTING

funcname = 'BAPI_PO_CHANGE'

EXCEPTIONS

function_not_exist = 1

OTHERS = 2.

IF sy-subrc EQ 0.

<<<<<<<Insert Block>>>>>>>

no_messaging = ''.

The same change also have to be done at the Include for BAPI_PO_CREATE1.

Include: LBBP_BAPI_POF20.

<<<<<<<Context Block>>>>>>>

....

ELSE.

CALL FUNCTION 'FUNCTION_EXISTS'

EXPORTING

funcname = 'BAPI_PO_CREATE1'

EXCEPTIONS

function_not_exist = 1

OTHERS = 2.

IF sy-subrc EQ 0.

<<<<<<<Insert Block>>>>>>>

no_messaging = ''.

Header Data

Release Status: Released for Customer

Released on: 21.12.2007 16:09:49

Master Language: English

Priority: Recommendations/additional info

Category: Consulting

Primary Component: SRM-EBP-CA-PRT Document Output / Forms

Subscribe | Add to Favorites

Note 883693 - ECS: PO output determination in R/3

[Former Member · Accepted solution]

Hi Muthu,

Excellent note (883693), issue is solved.

Thanks!

Ezequiel

[Former Member]

Hi Muthu,

Not sure if you're around! I need ECS PO from SRM to create IDOC when replicated to ECC, Please can you suggest, the transferred PO's don't have PO output type messages either, what I'm missing and how can get IDOC created in ECC for SRM ECS PO. Thanks.