Questions about Extended classic scenario

Question

Hi gurus,
I'm working in SRM 5.0, ECS, backend ECC 6.0 (only one backend).
Everytime a SC is being approved a SRM PO has be created. Then a copy of this PO  has to be created in ECC with document Type ATT and the same number of the SRM PO.
I have two questions
First of all I need to know the settings to make in 'Define objects in backend system' (for every purchasing Group and every Category ID, I need to create always PO in backend).
P.Gr   Category ID  Source System      Internal proc.                              External proc.
        *                 TRDCLNT011         Always external procurement        PO if item data complete, otherwise P.Req.
Is this correct?
Secondly I need to understand the logic for number range definition
SRM Activities
1 - Define number range for Shopping Cart
I Need to create a SC number range
01 1000000000 - 1999999999
and then associate this range (01) to SHC transaction type ('Int.n' field)
2 - Define a number range for local PO
LO 7000000000 - 7999999999
and then associate this range (LO) to ECPO transaction type ('Int.n' field)
3- Create a new transaction type 'ATT' (backend PO)
4 - Define a number range for backend PO
PO 7000000000 - 7999999999
and then associate this range (PO) to ATT transaction type ('Int.n' field)
ECC Activities
1 - Define a number range for document type ATT
XX 7000000000 - 7999999999
and then associate this range (XX) to ATT Document  type 'External
Is this correct?
I'd really appreciate your help
Points will be rewarded
Thaks in advance
Best regards
Gg

Answer 1

Hi. It all sounds about right.
I don't think the define backend docs does a great deal in ECS, you always get a PO with extended classic. If you ever want anything but a PO, a reservation for example, you have to not use extended classic for those items.
The number ranges look OK, although I think you only need 1 number range for the backend/local POs, it should all go in line on its own. It's been a while since I got an ECS system going so it is hard to remember.
The thing to do is try it in a test system and see what happens.
If anything goes wrong let us know on SDN what error messages you get and we should be able to help.
Regards,
Dave.