Skip to Content

wbs field not showing up on FB60's main screen

Hi All,

I want the wbs screen to show up on the main screen of FB60. I don't see it currently

I have to double click on the line to see it

I want it to appear like below

I have checked Shdo, but I can't figure out how to set this up. I have looked at the shdo wikis on scn, but the screen variants I am creating aren't showing up in FB60.

Is SHD0 the way to achieve this? can someone please tell me how to do this?

without-wbs.png (13.7 kB)
with-wbs.png (48.7 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Mar 22, 2017 at 04:38 PM

    I have read a lot of the wikis and all of them talk about making a field invisible or required. The problem I am facing is that I need to get the wbs field which is on the second screen, to the main screen. I don't see any option of doing that.

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 23, 2017 at 04:06 PM

    Hi Bro,

    Please follow the below steps and change the requirement as per your request and take help from abaper also if you required on this.

    Call transaction OXK3 (Maintain User Defined Coding Block Fields)

    Under menu 'Account Assignment Fields' choose Expert Mode.

    In same Menu, Choose 'Add Field', this will add field to CI_COBL Structure.

    In same menu, Choose 'Add Field BI' (For Batch Input)

    Now If you are in ECC 6, follow instructions below (from note 1451330)
      1. Call transaction SE11 for the table BSEG in change mode. Delete all existing fields in CI_COBL from BSEG (if these exist). Also check whether each of the fields in BSEG are the same type as those in CI_COBL. If not, do not proceed; otherwise, BSEG may have to be converted later. When using this procedure, make sure that no fields are duplicated when subsequently adding CI_COBL. At most, new fields should be added only if they did not already exist in BSEG. Save the table definition but do not activate it yet. The system requests a transport request. Exit transaction SE11.
      2. Call transaction SE11 again for BSEG in change mode. In the menu, choose "Goto -> Append Structure" and then choose "Create Append" in the dialog box. Select an APPEND name in your namespace (for example, "ZZBSEG"), enter a short description on the follow-on screen, position the cursor on the first line in the field list and choose "Edit -> Include -> Insert" from the menu. In the following dialog box, enter the structure CI_COBL. Save and activate it. In the following dialog "Inactive Objects", select both entries TABL BSEG and TABL ZZBSEG to activate them together. This may take several minutes because the dependent DDIC objects have to be activated.
      3. Use transaction SE11 to check that the table BSEG is active and the runtime object is consistent (in the menu, choose "Utilities -> Runtime Object -> Check").
      4. Use transaction SE09 to check again that both of the objects LIMU TABD BSEG and R3TR TABL ZZBSEG are contained in the same transport and can be activated together during the import. Otherwise, a complex conversion of BSEG is required in the follow-on systems.

      "Having done, all above, new field should appear at line item level, value in same should update in BSEG".

      Hope it helps

      Thank You

      Repakula Manoj

      Add comment
      10|10000 characters needed characters exceeded

    1. Mar 28, 2017 at 08:26 AM


      You Can Create a Screen Variant and Activate the same for respective T-Codes.

      SHD0 --> FB60

      Use new Button and Create a New Screen Variant.

      Add comment
      10|10000 characters needed characters exceeded