Local transaction types and Backend PO types

[Former Member]

We are using SRM 6.0 using Ext Classic. We are taking External requirements from R3 (purchase requisitions) and creating POs in SRM.

Our problem is the following.

We want to create four different document types of POs (ZPO, ZCS, ZIA, ZAD). The problem is that when we are creating the purchase order from the external reqt (through sourcing hub), we select the document type ZCS or ZIA or ZAD but SRM always creates ZPO locally and in R/3..

Our question is: How can we create the PO according to the user's selection of transaction type and make sure that the correct PO type is created locally and in the backend. We have maintained all four transaction types in attribute BSA and also in R/3.

Thanks!

-Bakulesh

[Former Member]

HI,

What value you have matained in the Attribute "DP_PROC_TY" in ORG Structure . I think you have to maintain all the four transaction type there.

Regards

kalandi

[Former Member]

Yes. DP_PROC_TY is meant for manual creation PO.

and you can specify the doc types desired for the PO.

Also please check that you have specified the internal no ranges for these doc types

and they lie in the range of the external no range you will define in the back end PO no range interval

and specify as external no range in ECC PO doc type.

BR

Dinesh

[Former Member]

Thank you all for your excellent responses/suggestions. The problem has been resolved. Once we connected SRM to the portal, the functionality was as desired.

FYI, for SRM 6.0 and beyond, the Portal is mandatory.

-Bakulesh.

[Former Member]

Hi. You can try BBP_ECS_PO_OUT_BADI BADI to see if that can influence the backend document type.

Regards,

Dave.

[Former Member]

Thanks Dave.

What about the transaction types for local POs ? How do we control them ? When a user selects the transaction type, he/she would like to see the same transaction type on the screen during processing/creation of the PO .

-Bakulesh