Customizing PO in Classic Scenario

[Former Member]

Hi Guru,

I have worked with SRM 7.0 in classic scenario.

I have to transfer purcher requisition from ECC into SRM and in the next step I have to create a purchaser order in classic mode (only in ECC ). I have problems about the PO customizing.

In SPRO --> Define transaction type, have I create a type document for backend PO? in BUS2201?

What are the customizing steps?

Thanks a lot

Kara

[laurent_burtaire · Accepted solution]

kara kara wrote:
(...)
In SPRO --> Define transaction type, have I create a type document for backend PO? in BUS2201?
(...)

Hello Kara,

no (PO is created in ECC backend)

You have to:

1- give internal number range for each backend document (SRM system)

IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Number Ranges > SRM Server Number Ranges > Define Number Ranges for Shopping Carts and Follow-on Documents

2- assign, depending on backend, number range to corresponding backend category type (SRM system)

IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Number Ranges > SRM Server Number Ranges > Define Define Number Ranges per Backend System for Follow-on Documents

3- define objects in backend (SRM system)

IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)

4- overwrite customizing if you have specific business rules using BAdI (SRM system)

IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Business Add-Ins > Follow-On Document Generation in the Backend System

for Purchase Order Purchase Order in Backend System

for Purchase Request Purchase Requisition in Backend System

for Reservation Reservation in Backend System

5- define R/3 PO number range and document type created based on SRM Shopping Cart (R/3 system)

IMG: SAP Customizing Implementation Guide > Materials Management > Purchasing > Purchase Order

> Define Number Ranges

> Define Document Types

6- give document type in R/3 system by populating BSA attibut (PPOMA_BBP trasanction) with PO document type value created in step 5 (SRM system).

Regards.

Laurent.

[ricardo_cavedini]

Hello,

SPRO would be relevant to customize local POs (BUS2201).

You have to customize PO transaction type in BSA attribute in PPOMA_BBP and create a number range.

The following number range customizing should be done:

a) at SRM side:
SPRO activity "SRM Server Number ranges" -> "Define number ranges for
shopping carts and follow-on documents"
RQ for purchase requisitions in the backend system
PO for purchase orders in the backend system
RS for reservations in the backend system

b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range;

- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range as "NoRge Ext" - table V_T161.

- Make sure that the SRM and R/3 number ranges match are exactly the same.

Regards,

Ricardo

[Former Member]

Thank at all!!!

In classic scenario can I create multiple backend PO types ? How I do to choose in sourcing cockpit the type to create in backend?

Best Regards

Kara