Custom field in RFFMEPGAX

[former_member188217]

Hi ,

I have a requiremnt to add one more field in Document journal report .

Need to include EBELN from BSEG table , saw some responses asking to check

Please check also in SPRO -> Public Sector Management -> Funds Management Government -> Information System -> Business Add-Ins (BAdIs) -> BAdI: Enhance Document Journal.

I am not sure how to go about , kindly advice.

[former_member182915]

Hello anju,

as you want to change standard report  RFFMEPGAX you need to do some enhancement as like do something like declaration, manipulation so you have to go for badi, or custom exit.  other option take access key change the code , but this will not maintain if u upgrade your sap.

Hope this will you.

[iklovski]

Hi,

This BADI won't be helpful for your need. As note 883122 specifies:

"

FMRP_RFFMEPGAX_EXIT

                       Using this BAdI the customer can process the lines in the Document  Journal. The data shown in the standard is basically the FMIOI content.  The BAdI gives the possibility to modify the display of this data.

                       Implementation FM_EF_HIST_REP_SPAIN enables the user to use four  additional columns in the document journal. This additional fields are  "open amount" (in both local and document currency) and "amount left"  (again in both local and document currency). To be able to use those  columns the customer must add the structure "IFMEFHIST" into the  customer include of the structure "IFMREPGAX" (structure used in the  document journal report). The open amount field is used to display the  actual non-consumed amount in every earmarked fund document line. The  amount left is used to display the part of a line amount that is not passed to the next year during the carryforward process."

The report in question is reading FMIFIIT/FMIO tables and cannot display fields from FI tables, e.g. BSEG.

Regards,

Eli

[Former Member]

Hi,

Well, in that report, standard fields predecessor document number(vrefbn) + predecessor doc.cat(vrefbt) should give them the same information as ebeln. Just run the report and pull theses two fields into the layout. If the value of vrefbt is 20, the document number in vrefbn is a PO number. 

Regards,

Ming 

[Former Member]

Hi Minghong  /  ELI

the requirement is to understand the Purchase order number for Invoice documents in the journal. for ex the SES acceptance and MIRO documents. at the moment the Predecessor number for these is the SES number not Purchase order number.

Now just by looking at these document lines its not possible to identify the PO number.

thanks in advance.

[Former Member]

Not sure if this what you are looking for, but perhaps you could fill the available customer field (USERDIM) at the time of posting. This field is available in FM Totals and Line Items tables and also in this report.

Check BAdI Fill Customer Field (definition FMPU_R_USERDIM). Carefully evaluate this solution though, as this can multiply dramatically the number of entries in these tables.

[former_member188217 · Accepted solution]

Thanks for the replies.

Solved with the below approach.

* Enhanced the structure IFMREPGAX by including the fields

* Go to below path

SPRO -> Public Sector Management -> Funds Management Government -> Information System -> Business Add-Ins (BAdIs) -> BAdI: Enhance Document Journal.

In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

Enter a short text for the implementation in the Short text for implementation field.

From the tab index, choose Interface.

The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

Save your entries, and assign the implementation to a development class.

Place the cursor on the method, and double-click to enter method processing.

Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.

* Save and implement your code. Return to the Edit Implementation screen.