Multiple G/L or Cost centres in IDOC_INPUT_INVOIC_MRM

[P561888]

HI All,

We are creating the Invoices through idoc, while creating the invoice we are unable get the multiple G/L or Cost centers.

This is FM ---IDOC_INPUT_INVOIC_MRM

We contact the SAP for this problem they came up with Customer exist EXIT_SAPLMRMH_015.

Could you please help me ...

Regards,

Bharani

[P561888]

Hi ,

Could any one come across this scenario....

Regards,

Bharani

[Former Member]

Hi,

while creating the invoice we are unable get the multiple G/L or Cost centers

What do you really mean by this?

Is your IDOC getting generated as per your exceptation or there is problem at sender side itself.

I think SAP has provided User Exits whereis you can code for population of Multiple G\L ir Cost Centers as you except.

Regards

Shital

[P561888]

Hi ,

Scenario is PO has the one or more G/L account or Cost centers , when creating INVOICE through IDOC it is considering only the FIRST G/L aacount or Cost Center ,But when we are creating the INVOICE manually i am getting the one or more G/L accounts or Cost Centers.

We have the talk with the SAP they have came with us with Customer-exist. they is the Customer exist EXIT_SAPLMRMH_015 . but i am unable to find the solution for this. please help me about this.

Regards,

Bharani.

[Former Member]

Ok, Thanks for clarification. The Solution could to extend IDOC Type to Include multiple INVOICE G\L Accounts or cost centers. You will have to use the User Exit provided by SAP to populated these additional fields in the IDOC.

For more information on extending the IDOC Type refer [Link1|/community [original link is broken];

Steps:
1. Create the Segments with the New fields Tcode WE31
2. Create the IDOC type (Extension) Tcode WE30
Add the segments here
3. Implement the Function module exits to populate the new segments in Outbound and to Process and update the New segments data in INbound.
TCODE CMOD.

Regards

Shital

[P561888]

No that method is not suitable, Is there any thing we can change in the user exist.

Regards,

Bharani