cancel
Showing results for 
Search instead for 
Did you mean: 

SWO_OBJTYPE_AFTER_IMPORT error in XPRA phase.

0 Kudos

Hi All,

getting below error while applying the abap patch SAPKA71101 in XPRA Phase.

Post-import method SWO_OBJTYPE_AFTER_IMPORT started for SOBJ L, date and time: 20100728183538

Object type 'BUS7030' generated successfully

Object type 'EMMAJOB' could not be generated

Function module 'BAPI_EMMA_JOB_JOBS_SELECT' is not defined

Function module 'BAPI_EMMA_JOB_CASES_CREATE' is not defined

Function module 'BAPI_EMMA_JOB_CASES_GET' is not defined

Function module 'BAPI_EMMA_JOB_DELETE' is not defined

Function module 'BAPI_EMMA_JOB_MESSAGES_GET' is not defined

Function module 'BAPI_EMMA_JOB_INTERVALS_GET' is not defined

Field BAPI_EMMA_JOB-BUSINESS_PROCESS_CODE is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-BUSINESS_PROCESS_AREA is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-EXTERNAL_JOB_NUMBER is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-TRANSACTION is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-DATE is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-TIME is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-USER is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-FIELDNAME is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-FIELDNAME is not defined in the Data Dictionary

Field BAPI_EMMA_JOB-FIELDNAME is not defined in the Data Dictionary

Errors occurred during post-handling SWO_OBJTYPE_AFTER_IMPORT for SOBJ L

SWO_OBJTYPE_AFTER_IMPORT belongs to package SWO

The errors affect the following components:

BC-DWB-TOO-BOB (Business Object Builder)

Post-import method SWO_OBJTYPE_AFTER_IMPORT completed for SOBJ L, date and time: 20100728183538

please guide me on how to proceed further.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Are you doing the patch individually? did you amke a test run or not?

Does this object din't showup in SPDD/SPAU modification adjustment object list during test run?

Please make the manula correction or go ahead implement next release of SP, as stated in S-Note 1500934 - EMMA Generation error EMMAJOB after implementing SAPKA71101.

If you still have problem, please raise an OSS message with SAP.

Regards,

Sitarama.

Former Member
0 Kudos

Try out note : 1500934.

Former Member
0 Kudos

Hi Draviya,

Same issue I have faced already in patching SAP CE 711 and I made a mistake that I was applying the SP one by one I mean first I have finished Basis and then I started ABAP, the solution for the same is in ABAP patch 3 I guess (till I remember), we were not able to solve it with the following steps given in SAPnote 415682

The error is not that serious that the upgrade needs to be halted. It is sufficient to perform an error analysis once the upgrade is complete. For each object type with errors, you can proceed as follows:

Start transaction SWO1.

Enter the name of the object type.

Choose 'Generate'.

If you are able to generate the object type, you can ignore the error in the transport log.

If you are unable to generate the object type, choose 'Display'. Check the status of the object type. To do this, choose 'Basic data'. If the object type has the status 'Modelled' (third field), you can ignore the error in the transport log. The reason is that modelled object types have no effect on the running system. The generation of these object types will be enhanced in Release 6.10.

If the object type does not have the status 'Modelled', choose 'Check'.

Analyze the error messages.

If the error was caused by a dependency on a customer object type (object type Z, Y), correct the customer object type.

We just took our last successfull backup and restored it and then I applied the patches in whole Stack for ABAP (all components) and it worked ...

All the best !

0 Kudos

Thank you Prateek your approach solved my problem..!

paul_power
Active Contributor
0 Kudos

Hi,

Please check and follow the steps of SAP note 415682 Generation error of BOR object types during upgrade

to resolve this error.

Check object EMMAJOB

If you need help repairing the object, I would recommend opening a message with component CA-EMA for assistance from SAP.

Regards,

Paul