Classic Vs Extended Classic Scenario issue

[Former Member]

Dear Experts,

We are implementing classic and extended classic scenarios to create service PO and material PO respectively. In the org structure attributes for the root org unit, the BSA attribute is set for ECPO (extended classic) and for ECS (classic), the BSA checkbox is blank. With this set up, the material PO (extended classic) is getting created successfully and items transferred to ERP. However, the service PO (classic) is not getting created in the backend. We have set the BSA attribute for ECS (classic) and unchecked the ECPO (extended). With this setup, the service PO (classic) is getting created. However, the material PO which has to be created as extended clasic is getting created as Classic scenario and taking the number range of classic PO.

The PO DOC_TYPE is ECPO for all POs irrespective of classic or extended classic if the BSA attribute is ECPO. Similar is the case with ECS. We want to implement scenarios - Classic (ECS) for service PO and Extended Classic (ECPO) for material PO. Can anyone help whats going wrong here?

Thanks

Abdul Azeez

[Former Member]

Hi Abdul,

Check for Badi BBP_EXTLOCALPO_BADI. This will fulfill your requirement.

Thanks

Ravi