How to configure the SRM system to deflate active GR non-valuated at the R3

[Former Member]

Hi,

We are using the extended classics scenario at the SRM 05 system. We are looking for a way to configure the SRM and/or the R3 systems, so that the PO at the R3 system will be created with active "GR non-valuated" check box.

Thanks,

Yaron Malka

[former_member206968 · Accepted solution]

Hi,

You can use bbp_doc_change badi to set the GR_non_val indicator or else use bbp_ecs_po_out badi to send this indicator to backend.

Regards,

Sanjeev

[Former Member · Accepted solution]

Dear Sanjeev,

Thank you for your response.

We have implemented BADI bbp_ecs_po_out but we cannot find how to be assisted by it.

Can you give us more details or directions?

Best Regards,

Yaron Malka

[former_member206968 · Accepted solution]

Hi,

You should try to set gr_non_val variable as X in structure ct_bapi_poitem.

Regards,

Sanjeev

[Former Member · Accepted solution]

Hi Yaron,

In case of multiple account assignments to a P.O item, that is multiple cost centres or multiple networks then the G.R Non valuated check box will get automatically checked in backend ECC system.

This is the standard SAP behaviour.

However you want to enforce the GR Nonvaluated check then you can call BAPI_PO_CHANGE at the time of P.O creation in ECC system and can mark the G.R Non valuated check box.

Please try this option and let us know the outcome to help you further in resolving the issue.

Regards,

Teja

[Former Member · Accepted solution]

Dear Sanjeev,

We did it but it dosen't work. This is our implementation:

method if_ex_bbp_ecs_po_out_badi~bbp_b46b_po_outbound.

data: lwa_bapi_poitem like line of ct_bapi_poitem.

loop at ct_bapi_poitem into lwa_bapi_poitem.

lwa_bapi_poitem-gr_non_val = 'X'.

modify ct_bapi_poitem from lwa_bapi_poitem

index sy-tabix

transporting gr_non_val

.

endloop.

endmetho

Best Regards,

Yaron Malka.

[former_member206968 · Accepted solution]

Hi,

Actually due to sap note 674421, this field is always set as blank while calling backend bapi. Instead you may need to use badi bbp_po_inbound_badi (method - before_bapi) in backend system to achieve this. Change gr_non_val as X for both bapi_poitem and bapi_poitemx structures.

Regards,

Sanjeev

[Former Member · Accepted solution]

I agree with Sanjeev,

we are following the same approach, since we want all account assignement categories flaged as "non-valuated" in R/3 backend.

Cheers

Edited by: Christian Bauersachs on Aug 10, 2009 10:41 AM