cancel
Showing results for 
Search instead for 
Did you mean: 

Configuration Backend Document generation SRM 5.0

Former Member
0 Kudos

Hi can anyone check the following settings we made.

We are using SRM 5.0 (server 5.5) and after shopping cart approval we want to create always Pur.Reqs in a SAP 4.6C Backend System.

The purchase requisition should be of type ZSRM in the Back End system.

We use Classic Escenario.

The settings for the number ranges is as follows:

*In SRM 5.0*

"Define Number Ranges for Shopping Carts and Follow-on Documents"

01 - 0020000000 - 0029999999 (number range for SHC)

ZQ - 4200000000 - 4209999999 (number range for Pur.Req in Backend) - both number ranges "internal"

In SAP Back End we defined for the Pur.Req:

Documento Type ZSRM with external number range ZQ

Number Range: ZQ - 4200000000 - 4209999999 (external)

After this we added in the Organizational structure (top node) attribute BSA: ZSRM - Logical system Backend (ENT100)(flag "Default")

in SRM 5.0 we after this customized:

"Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)"

Purchasing group "50000116" - Category ID "*" Source System "ENT100" (Logical system Backend) - 3 "Always external procurement" - 1 "always Pur.Requisistion"

As far as I know , this should be enough to be able to generate Pur.Req. in hte Background system.

Please can anyone confirm or tell me what is missing?

Thanks,

Aart

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Aart,

I think you have done all necessary settings, looks like you may have to do just one more settings.

In SRM in SRM server number ranges setting, you may have to set "ZQ" as No. Range PReqs in the config setting "Define Number Ranges per Backend System for Follow-on Documents".

Hope this should create backend PR for your Shopping Cart.

Hope this helps.

Please reward points if the hint is found useful.

Thanks

Venkat

Former Member
0 Kudos

Aart,

In Define Backend System for Product Category", try leaving the source system blank. When we used local system name there it caused us some replication problems.

Also, what follow-on documents got created when the shopping cart was approved?

- Suren

Edited by: Suren on Feb 12, 2008 9:30 PM

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks Guys,

Problem solved. Excelent work

Aart

Former Member
0 Kudos

Hi guys ,

Thanks for the input,

For the "Define Backend System for Product Category" customizing I put "*" Source System "ENT100" (Logical BackEnd) - Target System "ENT100"

We replicated the product groups from the BackEnd.

Creation of the Shopping cart results in WF10000031 (two step) which we can autorize via the WEB.

This leaves the autorised and liberated shopping cart in BBP_PD with status:

Stats:

Status Description Inactiv

HEADER I1015 Awaiting Approval X

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1106 Shopping cart ordered

HEADER I1129 Approved

Running report CLEAN_REQREQ_UP does not result in creating the Pur.Req in the Back End.

Do we need to activate a BADI?

What steps are involved after approval of th SHC in the generation of the Pur.Req. and how can I check in which stadium our process is stuck?

Thanks for any reply.

Aart

Former Member
0 Kudos

Hi,

Looks like you are done the basic requirements, try to create shopping basket and let us know if you have any further issues.

Regards

Sreedhar Vetcha

Former Member
0 Kudos

Aart,

In "Determination of Traget System using Product Categories", you need to specify

Product Category - * (for all)

Source System - (leave blank. I ran into problems when I used local SRM system name here)

Target System - Your Backend R/3 system.

- Suren