How to Add Coding Blocks in SAP FI – Enjoy Transactions?

According to the definition of “Customization,” it refers to changes made to a product or service to suit a specific purpose. This purpose can vary, such as making adjustments to standard processes. In SAP terms, customization often involves modifying or adapting the system to meet your business requirements. For example, understanding how to add coding blocks in SAP FI is crucial when adjusting the standard SAP processes to align with your business processes.

In this instructional tutorial, we would like to show you how to add coding blocks in SAP FI by including a custom field in FI transactions like FB01, FB50, FB60, FB65, MIRO, etc., at the General Ledger Detail level as a Coding Block Field.

Alert: SAP prescribes to play out this movement in a Test Climate first. The progressions are kept in the test framework in a vehicle demand and can hence be shipped into different frameworks.

The output will look like below

Custom Field in FB01
Custom Field in FB50
Custom Field in FB60
Custom Field in FB65

Announcement

Pre-Requisites

  • You require a test framework to incorporate coding fields.
  • To incorporate coding fields, you require the accompanying approvals:
    • New field consideration in coding block X_COBLMOD
    • Support of cross-client tables S_TABU_CLI
    • Word reference approval S_DEVELOP
    • Transport approval S_TRANSPRT

Your framework is running on a HANA data set with a straightforward table BSEG. In this climate, you are not generally permitted to add the custom fields to table BSEG through changes. All things considered, you need to add the incorporate CI_COBL to BSEG utilizing an Affix. Check whether the table contains the incorporate CI_COBL.

In the event that this isn’t true, continue as depicted in SAP Note 1451330.

Recommendation

We suggest that you make an idea for your own coding field as soon as could be expected and roll out the fundamental improvements to the coding block.

Caution

  • Characterize the last configuration (information type and length) for the new coding field quickly. You can’t roll out resulting improvements to the field design or erase a coding field whenever it has been incorporated utilizing standard techniques (see likewise the extra specialized data).
  • Check whether a reasonable standard SAP coding field as of now exists that satisfies your necessities. If so, utilize that field, in any case, make another coding field.
  • When a client has been hailed as a creation client in a framework, the Incorporate fields capability is locked for that framework. This guarantees that no ensuing changes can be made.
  • The framework adds the recently included coding fields to the current ABAP Word reference tables.
  • Changes to the ABAP Word reference tables can, on account of blunders, lead to a deficiency of information. Do a reinforcement before you embed coding fields.
  • During the execution of these Word reference tasks, no different clients ought to be working in the framework. Some other clients working in lined up in the framework could be hampered by the DDIC exercises.
  • Cross-client objects are kept up with this capability. The upkeep of these articles in this manner influences every one of the clients in the framework.

Let’s Design

  1. Go to transactions OXK3
  2. On the Menu-Bar, click on “Account Assignment Fields” –> “Expert Mode“.
Tcode: OXK3

3. Create Domain: Make the space of the new custom field, picked any name as expected according to the naming shows of your undertaking.

Note: The total usefulness is just accessible for the fields of information types Roast and NUMC in all exchanges that utilization the coding block. For different information types, for example, sum and date fields, issues can happen in different exchanges, and they must be kept away from with a client explicit change.

Provide the required data type, preferably CHAR or NUMC

Save and Actuate the Space.
Whenever required, you can enter fixed values or a really look at table for this space.

4. Create Data Element: Make the Information Component of the new custom field, picked any name as expected according to the naming shows of your venture. While making the information component, we will utilize the space made previously.

Click on “Create Data Element”
Give the name of the data element.
Give the earlier created domain “ZZPER” and provide the field label of this field.

Kindly note that the field name of this field must be 10 characters in length, so conclude a significant name thinking about this as a top priority.

5. Add Field: Presently we should add this field in a client incorporate “CI_COBL”.

CI_COBL has been remembered for every one of the tables pertinent to the coding block, so that new field can hence be placed in these tables.

Vital data beneath.

Press Enter and proceed.

Give the name of the field and the above created data element.

Save and Actuate the Custom incorporate construction above.

Caution: DDIC enactment in the update run can consume most of the day. To keep away from issues brought about by ended initiation, put down a point in time out of something like 30 minutes for exchange processes. On the other hand, you can likewise actuate CI_COBL in group mode, as depicted in SAP Note 2283388. Or on the other hand you could need to take help from Reason for the legitimate enactment of all the DDIC objects.

6. Add Field BI:

This construction is utilized in FI for entering reports in group. In the event that you have been working in master mode and have utilized a configuration other than Singe for your new field, you likewise need to add a field with design Roast and a similar result length as your new field for use with this incorporate. You might need to characterize a fitting information component and the applicable area too.

Press Enter

Save and Initiate the Custom incorporate construction above.

7. If you are using a system having SAP Basis Release less than 7.00, then the new field must be added to the end of table BSEG.

While, as of SAP Premise Delivery 7.00, you can add your own coding fields to table BSEG without alterations. To do this, you need to remember the construction CI_COBL for your Add structure. This Affix construction can be remembered for BSEG subsequently so all custom fields are remembered for table BSEG certainly through CI_COBL. For more data about this strategy and for a depiction of how you can thusly still trade out client explicit fields into an Add structure, see SAP Note 1451330.

At this point, you can see your Custom Field as beneath:

8. Add Control Entries

Select the custom field as beneath

Then add this control section. Utilizing the Add control passages capability, you can keep up with the suitable framework control tables naturally. This makes the new field accessible in Altering very much like some other standard SAP field.

Note:
A limit of 18 client explicit fields can be included the standard framework. In the event that you require more fields, you really want to make gatherings of fields for the field determination control in FI and MM as illustrated in SAP Note 885181. The gathered fields could them at any point just be initiated or deactivated together or characterized as obligatory fields.

Counting Client Fields in Appreciate Exchanges: In the section variations of the Appreciate exchanges, you can decide up to five conventional fields under the specialized name ACGL_ITEM_GEN-GEN_CH and possess these fields with your custom fields. PFB the connection:

9. Create Sub-screen:

Make the sub screen which will be utilized to show this field on certain exchanges having coding block fields.

Create the sub-screen.

In the wake of creating, the sub-screen will look like beneath:

Field Status Group Configuration

Indeed, assuming you imagine that with this you will actually want to see the custom field on the appreciate exchanges, you may be off-base. With these means, we have empowered a custom field accessible to be utilized like some other typical field.

Presently, to see this field on the screens, you should make it as required/discretionary by characterizing the FIELD STATUS variation for the Posting Keys under the necessary organization code field status variations.

the IMG way to accomplish this is as per the following:

Select this row and navigate to “Field Status groups”

Double tap on the above line.

Here you can choose the field status gatherings and make the custom field as required/discretionary in the “Extra record tasks” part of the field status bunch.

As a matter of course the custom field is set to “Stifle”, we made this to “discretionary passage”

Maintain Accounting Configuration: Posting Keys [TCode: OB41]

Here you can empower the custom field for different posting keys. We attempted to empower this for posting key 41 – Charge Passage

Double click on posting key 40 line.
Click on “Maintain Field Status”
Double Click on “Additional account assignments”

Conclusion

In this blog post, we explored how to add coding blocks in SAP FI by including a custom field in FI transactions like FB01, FB50, FB60, FB65, MIRO, etc., at the General Ledger Detail level as Coding Block fields.

Please note that there are certain risks involved in this activity. Therefore, ensure that you perform this task with great care and necessary precautions, especially when learning how to add coding blocks in SAP FI to avoid potential issues in the financial module.

 

YOU MAY LIKE THIS

SAP ABAP Checkpoint Group – Chase the Mysterious SAP Issues with a Smile

Best Practices for SAP ABAP Development: A Comprehensive Guide

4 Useful Tips on ABAP and ABAP on HANA

WhatsApp WhatsApp us