Error while Creating Business partner in FPP1

[Former Member]

Hi,

I can't create Business partner in standard T.code FPP1 in Test System and getting the following error

"Application object BUPA: Table EBUPD does not exist".

Kindly help me in solving this issue.

[Former Member · Accepted solution]

Hi Venkatesh

Please add the message class and message number - in this case R1 149 - next time you post a problem.

There's probably an issue with your setup with for the Business Partner Screen Layout (area menu BUPT).

The error is raised, because the EBUPD is not a table assiciated with the Business Parter (Application object BUPA). See transaction BUSG or table TBZ1H. It is in fact a dynpro structure.

Now there's a table that links the dynpro structure fields to the db table fields, which should translate the structure EBUPD into table EKUN fields: TBZ1C. Technically, this is done in function BUS_DYNFLD_TO_DBFLD_CONVERT and it returns the dynpro structure instead of the DB table if there's no corresponding entry in TBZ1C.

So please check if you can find following entry in TBZ1C (client dependent):

OBJAP  DYNPTABNM  DYNPFLDNM  DBTABNM  DBFLDNM
-----  ---------  ---------  -------  -------
BUPA   EBUPD      +          EKUN     +

Or via transaction BUSP - Screen field --> Database Field

If the entry is missing I suggest you add it.

Yep

Jürgen

[Former Member]

Hi Jürgen,

Issue is after creating in the table TBZ1C. But my question is same entries is not present in development which is working fine?

Thanks,

Venkat

[Former Member]

Hi Venkat

That depends on the customising of the screen layout and the field grouping.

The related transactions are mainly:

BUS1 - Applications

BUS2 - Field groups

BUS3 - Views

BUSC - Field grouping criteria

BUSJ - Field grouping per activity

BUSO - Field grouping per BP category

The customising determines the fields that are in use for BP and what attributes, like mandatory, hidden etc., are assigned, which can be dependent on the acitivity, BP category etc.

If a field is going to be used on the screen, it goes through the function BUS_DYNFLD_TO_DBFLD_CONVERT.

Without seeing all the related customising, it's impossible to locate the delta causing the problem. One thing I want you to check though:

Transaction BUS1 - Applications

Double click on ISU - SAP utilities

Is the active flag set?

Otherwise, I recommend to start comparing the customising of the Views (BUS3) with ID ISU210 to ISU420 and check the corresponding Field groups (BUS2) around the 400 area.

Yep

Jürgen