User attributes in extended classic mode

[Former Member]

Hi,

If i want to use the system in extended classic mode, what should i maintain in the attribute of BSA in the organization structre?

Should i maintain 1 entry for document type ECPO for SRM system and an another entry entry EC for the backend system.

Thanks,

Vignesh

[Former Member]

for example if you create a direct material PO's you have to maintain this attaribute DP_PROC_TY

To ensure that the documents can be transmitted to the back end, you have to maintain

corresponding transaction types, document types, and number ranges in Enterprise

Buyer and respectively in the back end system.

Whatever PO transaction type you may use and it must be equivalent to ECC document type.

and number range must be same srm and ECC since SRM only determines the number range for this.

[Former Member]

Thanks for the clarificatyion.

Thats means to if i need to use only extended classic, then i need to need to hav transaction type ECPO & number ranges configured in the backend as well as SRM system right?

[Former Member]

You need maintain these in backend customizing, error will occur and can be monitored via RZ20.

Here is the relevant customizing path in backend. (tr:SPRO)

Materials Management

Purchasing

Purchase Requisition

Define Number Ranges

Define Document Types

Purchase Order

Define Number Ranges

Define Document Types

Regards

Lauren

[Former Member]

Hi

Yes , You can maintain Both what you have mentioned.

In some cases where the client will be using both the scenario (classic & extended classic)

Regards

Ganesh Kumar.G

[Former Member]

The entry of the back end document type with the corresponding logical system should work fine.

DV