Skip to Content
0

how to add custom field at the header level of enjoy transaction FB75.

Mar 26 at 07:22 AM

58

avatar image

Hi All,

I have created a custom field using oxk3 and then appended it in BSEG.

and then created screen and transaction variant by using t-code SHD0.

and then added my custom field to enjoy transaction using SPRO.

Now i can see it in enjoy transaction FB75 at item level.

But what i need is to get it at header level.

can anyone please suggest me , what should i do to achieve it?

Thanks.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Raymond Giuseppi
Mar 26 at 09:30 AM
0

Look at the BAdI FI_HEADER_SUB_1300 (allow country filter) and from BADI_FDCB_SUBBAS01 to 06 for one without active SAP implementation as those screen BAdI don't allow multiple implementations.

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi sir,

when i m trying to search for a BADI by putting breakpoint in se24 on CL_EXITHANDLER=>GET_CLASS_NAME_BY_INTERFACE , i am not able to see FI_HEADER_SUB_1300 there but i can see BADI_FDCB_SUBBAS01 to 06. can u please guide me little more how to do it.

0
  • Read the BADI_FDCB_SUBBAS01 documentation.
  • Look at sample provide by SAP
  • Then look for a BAdI without active implementation, as you need one not yet used by SAP.
  • Copy and adapt the sample function group (BADI_EXAMPLE_FDCB_BAS) in your namespace
  • Create an implementation
  • If BKPF appended fields required, create an apend to structure INVFO, BSEG and coding block are already included
  • Add your appended fields in the dynpro with ddic reference to structure INVFO
1

Hi sir,

That day i had implemented it successfully but i am having one doubt.

what we will need to do if all BADI_FDCB_SUBBAS01 to 06 are already implemented?

Thanks.

0
  • Pray/Wait for a 07 BAdI
  • Analyze option to deactivate a SAP implementation actually not required
  • Deactivate a required SAP implementation, replace it with yours, merging fields and logic of SAP and your implementations.
  • Go to dirty solutions ranging from popup-screen with input fields raised in BAdI/Substitution rules to change of the standard with sscr keys...

0