SRM confirmation posting GR in ECC with RFC user id, need to enhance

[Former Member]

Hi,

My client requirement as below...

When we do confirmation in SRM, it's posted as GR in ECC. But the created user as "RFC user", but we need to post GR with the SRM user (Which user id posted confirmation).

If you know the Badi / Table...pls share with me.

Thanks in advance for providing solution.

Sathya

[former_member198532]

We have a similar requirement and will start working on this topic.

Check OSS note 938411 to fix this issue.

rgds

Vinod

[Former Member]

Hi Sathya,

Also, since Service confirmaations are created differently, they use the BAPI_ENTRYSHEET_CREATE you would need to look at the following.

9 SAPLMLSR FORM SHEET_INIT

8 SAPLMLSR FORM ENTRY_SHEET

7 SAPLMLSR FUNCTION MS_SERVICE_ENTRY

In subroutine SHEET_INIT,

ESSR-ERNAM = ESSR-AENAM = SY-UNAME.

Also the BAPI Interface structure does not contain the field username.

Hope these answers help you in your query.

Kind Regards,

Matthew

[Former Member]

Hi Matthew Stapleton ,

Thanks for your reply. But my question is how to enhance on standard BAPI ? Is it possible thru' BADI enhancement?

If you have any idea / solution..Please share with me...

Thanks in advance...

Sathya

[Former Member]

Hi..

try to use implicit enhancement..in ECC most of BAPI FM is coming with enhacement spot too.. try it..hope will work...

Saravanan

[former_member1150717]

Hi,

apart from above situation we have different situation,

Actually when any accounting document created against any SRM confirmation document at that time System user ID is getting displayed. But our customer wants instead of posting accounting document with system user ID it should be posted with respective user's ID.

Whenever any accounting document gets created against Confirmation/GRN documents at that time system should use user's ID instead of System ID.

Please help us in above situation.

Regards,

Manish

[Former Member]

Hi Sathya,

Please check the following answer:

(1) doing a confirmation in SRM system wich creates an idoc with basis

type MBGMCR

==> display idoc with we02

==> display data records for structure E1BP2017_GM_HEAD_01

==> field PR_UNAME = the user who created the gr !!!!

(2) posting the input idoc in backend system

==> display idoc with we02

==> seen in data records that PR_UNAME is the user who created

gr !!!

(3) se16 for mkpf material document header:

==> mkpf-usnam = rfcuserbbp !!!

(4) analysing BAPI_GOODSMVT_CREATE:

• map head to internal structure *****************

CALL FUNCTION 'MAP2I_B2017_GM_HEAD_01_TO_IMKP'

EXPORTING

BAPI2017_GM_HEAD_01 = GOODSMVT_HEADER

CHANGING

IMKPF = S_IMKPF.

S_IMKPF-USNAM = SY-UNAME. !!!!!!!

==> Sy-uname is actually the RFC-user defined in the srm system

with sm59

I would recommend you the following modification in function module

BAPI_GOODSMVT_CREATE:

...

• map head to internal structure *****************

CALL FUNCTION 'MAP2I_B2017_GM_HEAD_01_TO_IMKP'

EXPORTING

BAPI2017_GM_HEAD_01 = GOODSMVT_HEADER

CHANGING

IMKPF = S_IMKPF.

• start of modification !!!!

• only for gr comming from srm system

if sy-uname = 'RFCUSERBBP'. """ replace !!!

S_IMKPF-USNAM = GOODSMVT_HEADER-PR_NAME.

else.

• standard

S_IMKPF-USNAM = SY-UNAME.

endif.

*end of modification

==> you have to replace 'RFCUSERBBP' with your own RFCUSER wich is

defined in your srm system, this is I believe the easiest way

to recognize that the modification only works for idocs comming

from srm (for all other idocs the standard coding should be

processed).

Hope this helps,

Kind Regards,

Matthew