A long time, I come across the following situation in many projects:

  • Copy of transactions: FBL1N, FBL3N and FBL5N;
  • Create unnecessary Z reports in FI;
  • Creating incorrect append (BSEG);

Although there is great material in SDN, enough for a good development, I realize that there is always the same dilemma. Many times I myself was the spreader of it was not possible to include a new field in FB02, for example. So I decided to centralize all this subject in a blog, and I hope to help everyone!


To make it easier I will separate the subject topics:


1 – Create new fields in transactions FBLXN


     There are two ways:

    • FIBF and EXIT

               Create new product:

            FIBF1.png      

            FIBF2.png

              You need copy the FM SAMPLE_INTERFACE_00001650:

            FIBF3.png

               Create new event 1650 for FM (Copy):

            FIBF6.png

            FIBF7.png

               Each row processed in reports (FBL1N, FBL3N and FBL5N) will pass through FM Z.

               The function module has the I_POSTAB parameter that will receive the amounts already filled by the standard.

               Simply fill out the new field in the parameter E_POSTAB.

               Observation: check with SY-TCODE which transaction it is being processed.

            FIBF8.png

               OR


    • BADI:

               Implements the standard definition FI_ITEMS_CH_DATA.

            BADI.png

               In CHANGE_ITEMS method simply fill the new field (parameter CT_ITEMS):

            BADI.png

            BADI.png

               The big difference is that the BTE processing is done line to line and BADI the standard “delivery” all report list.

     The two forms is necessary create the new fields in the structures RFPOS and RFPOSX.         

  RFPOS.png

  RFPOSX.png

     You need to run RFPOSXEXTEND via SE38 program (all environments).

     I advise you to include the execution of the program RFPOSXEXTEND in task of your request.

     ID = R3TR and TYPE = XPRA.

SE09.png


2 – Change dynamic selection FBLXN

     Yes, it is possible! Don`t worry!

     First step, you must identify the logical database used by the standard in the transaction.

         

Transaction
Program
Logical DataBase
FBL1N RFITEMAP KDF
FBL3N RFITEMGL SDF
FBL5N RFITEMAR DDF


    





     Expand the logical database in SE36:

  SE36.png

  SE36.png

     Choose option: Copy (F7)

  SE36.png

     There is only one lock of this procedure is allowed only include some fields tables for each transaction.

     Basically the tables are displayed in the table list in transaction SE36.

     Obs.: Check SAPNote 310886.

     For example FBL1N:

Tables.pngTables.png

   In this case, the new field it was included in BSIK. Just click on the chosen table.

   Complementing the issue, you can also include standard fields that are not delivered by default.

  

   It is possible create new box, for example, 04 Test.

   This way you will get a new box of courses in the dynamic selection in the transaction.

   Choose the new field and which folder should be included.

/wp-content/uploads/2015/06/campos_730581.png

FBL1N.pngFBL1N.png


3 – Change screen using coding block

     This is the most critical of all item, especially because I myself was the propagator of this idea was not possible.

     First step. Create new fields in Structure CI_COBL.

     Attention: BSEG activation among other important tables.

    

     Transaction OXK3:

  OXK3.png

  CI_COBL.png

     The same step for Add Field BI, but the Structure is CI_COBL_BI.


     The step more important, add new append structure in BSEG.

     The field names must always start with two Z.

  BSEG.pngBSEG.png


     The next steps are customizing. 4 basic steps.

     1 – Identify which release keys should display the fields in the transaction. Setting should be made in OB41, enabling the visualization of fields.

     Example: ZZBSEG (Workflow).

  OB41.png

     2 – Identify the status-field groups that need to be modified in OBC4 (OB14), determining in ledger account level visualization of the field.

  OB14.png

     3 – Identify the types of release, account type and operating class, in the OB32 transaction to determine which types of accounts fields must be displayed.

  OB32.png

     4 – Make the setting in the table TCOBX via SM30 to determine the modification group for the field you can modify the field information.                     

  SM30.png

     RESTRICTION:   

  • In the coding block of the system you can create your own fields.
  • The new coding fields can then be used in FI General Ledger accounts, MM Inventory Management and MM Purchasing, and are also updated in the line items created in the Controlling applications.
  • The new coding fields cannot be used for account type D or K.
  • SAPNote 1607020.


4 – Change functions in transactions FBLXN

     Under construction…





To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply