Post Support Package Stack 16 to ECC6.0 Errors in objects TBSEG & T_BSEG

[Former Member]

Hi,

At the weekend we applied SP Stack 16 to our production environment. This was fully test in QA with no problems. We have also applied the same stack to other production systems without error.

Unfortunately with this production system we have a serious issue that we've raised a very high message with SAP that is causing core transactions related to finance to dump. The only problem that occured during the package import was the system got stuck on phase "TBATG Conversion DDIC Objects". At this point I had to restart the SAP system and SPAM.

We have two dumps appearing every few seconds as the following transactions are used::

FB05

FBV0

FBV1

MIRO

FF.5

FBZ3

FB50

Dump 1)

CONNE_IMPORT_WRONG_STRUCTURE

Error when importing object "T_BSEG".

Error in the ABAP Application Program

The current ABAP program "SAPLF005" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Dump 2)

CONNE_IMPORT_WRONG_STRUCTURE

CX_SY_IMPORT_MISMATCH_ERROR

Error when importing object "TBSEG".

Error in the ABAP Application Program

The current ABAP program "SAPLTAX1" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

We did start yesterday morning with "DDIC_INCONSISTENCY" dumps where nobody could access any transactions, however SAP helped at this stage by getting us to generate and activate the table BSEG by unlocking first. We are now left with the ABAP dumps on certain finance transactions.

It is now day 2 and even though the call is V.High, feedback has been slow.

Has anybody experienced a problem like this before and if so how did you resolve?

Kindest regards,

James

[Former Member]

Hi my friend

Did you have an interruption during importing SAP_BASIS? What error is it if you proceed in SPAM, a dump as well?

Also please provide your import buffer:

tp showbuffer <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.pfl tag=spam

Regards,

[Former Member]

Hi Fan Yu,

Think your on the right track. Since logging the message we've done some digging and found during import of SAPKH60016 there were some errors. Even on the fourth attempt to import it appears successful (RC=4 with warnings), however certain steps were missed relating to BSEG:

As we have faults with finance it may be worth seeing if SAP can reapply the SAP package or even try going to SAPKH60017.

Here are some warnings in the log:

LANGTABDBSEG was not imported in this step

LANGTABDCKI64A was not imported in this step

LANGTABDEMBEW was not imported in this step

LANGTABDERSALV was not imported in this step

LANGTABDKALM was not imported in this step

LANGTABDKALO was not imported in this step

LANGTABDKEKO was not imported in this step

LANGTABDKONV was not imported in this step

LANGTABDLIST_OF_RELEASING was not imported in this step

LANGTABDOIB01 was not imported in this step

LANGTABDOIB06 was not imported in this step

LANGTABDOIFSPBL was not imported in this step

LANGTABDOIG_TVFTK was not imported in this step

LANGTABDOIH5 was not imported in this step

LANGTABDOIJTS was not imported in this step

LANGTABDOIO_CM_SPROC was not imported in this step

LANGTABDRK70D was not imported in this step

LANGTABDROIL_HELP was not imported in this step

LANGTABDSHP_DELIVERY_ITEM_CREATE was not imported in this step

LANGTABDT156F was not imported in this step

LANGTABDT156W was not imported in this step

LANGTABDT156X was not imported in this step

LANGTABDVBFA was not imported in this step

LANGTABDZCXCM was not imported in this step

LANGTABLJ_1BNFLIN_SD was not imported in this step

LANGTABLOIB06 was not imported in this step

LANGTABLOIG_TVFTK was not imported in this step

LANGTABLOIJTS was not imported in this step

LANGTABLOIO_CM_SPROC was not imported in this step

LANGTABUCIFOBJINFT was not imported in this step

LANGTABUCIFTXTPOOL was not imported in this step

LANGTABUEWUPAKT was not imported in this step

LANGTABUJ_1BAJT was not imported in this step

LANGTABUT003T was not imported in this step

I'm awaiting SAPs response.

Is it possible to transport the package again either via STMS or SPAM. What is the likely outcome from SAP?

Kindest regards,

James

[Former Member]

Ok, you didn't provide me the tp buffer but it does look like you have an unfinished import left in the queue, indicated in the log, and some of them are critical and corrupted during the import last time.

Run this TP command and then finish it in SPAM, before starting make sure there's no other activities in the system:

tp R3I ALL <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8

-Dsourcesystems= tag=SPAM

Regards,