Know if a GR is created from SRM or ECC

[RicardoRomero_1]

Hi all,

Is there any way to know if a Good Receipt is created from SRM or if it's created directly in ECC ?

I have a requirement in which when the users are displaying a GR in ECC they need to know where the document is coming from (ECC or SRM). So I need to add something in the screen to identify this, but first I need to know how to know it.

I thought in check the field MKPF-USNAM and see if it's the RFC user, but I don't like to put a hardcode in the validation, any way there are different RFC users in each system (DEV, QA, PROD...) may be i can create a custom table to store the RFC users and check this table, but I don't like so much this solution.

The field AWSYS has always the same logical system.

SRM 7.0 Extended Classic Scenario

Thanks in advance.

Regards,

Ricardo.

[Former Member · Accepted solution]

Hello Ricardo,

Your question got me thinking. After a lot of debugging, i found that if you call FM SREL_GET_NEXT_NEIGHBORS in ECC with parameters like shown in attached image,the idoc number and the logsys from where idoc was created is returned as shown in the image.

with this it can easily be known if the GR was posted out of SRM.

Let me know if this helps.

Regards,

Sushil.

[RicardoRomero_1 · Accepted solution]

Hi Sushil,

Many thanks to investigate it. This solved my issue !
Thanks again !

[laurent_burtaire]

Hello Ricardo,

one solution (but with much more developments) is to transfer a header CUF (a XFELD field) from SRM to ECC: if it is set, confirmation was created in SRM, if not set, confirmation was created in ECC.

Confirmation transfer between SRM and ECC is managed by BBP_PD_CONF_TRANSFER function modul.

In include LBBP_PDF0B, entry sheet are managed by SPOOL_ES_CANCEL and SPOOL_ES_CREATE, whereas for GR, it is IDOC_GR_CREATE module function.

Regarding GR, you will have to use a specific FM to manage CUF transfer.

This FM will be called by META_GOODSMVT_CREATE FM through BAdI definition name BBP_DRIVER_DETERMINE.

It will be a copy of corresponding FM from BBP_FUNCTION_MAP table.

Inside this specific FM, you will have to manage importing parameter IS_CUF_HEADER by calling a copy of BBP_ALE_GOODSMVT_CREATE FM in order to manage CUF data.

As a consequence, you will have to manage an extension for IDoc basic type MBGMCR01 or create a new one from standard copy.

Same CUF must be maintained in ECC.

For ES, you have to do the same.

Regards.

Laurent.

[Former Member]

Hi Ricardo,

I think field MKPF-USNAM which will have RFC user name is the only clue to find out.

Can you can use of TVARVC (variant variable) table in your development ? Here you can maintain the SRM RFC user id for checking.

Best Regards,

Anil